Kconfig 9.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270
  1. #
  2. # USB Miscellaneous driver configuration
  3. #
  4. comment "USB Miscellaneous drivers"
  5. config USB_EMI62
  6. tristate "EMI 6|2m USB Audio interface support"
  7. ---help---
  8. This driver loads firmware to Emagic EMI 6|2m low latency USB
  9. Audio and Midi interface.
  10. After firmware load the device is handled with standard linux
  11. USB Audio driver.
  12. This code is also available as a module ( = code which can be
  13. inserted in and removed from the running kernel whenever you want).
  14. The module will be called audio. If you want to compile it as a
  15. module, say M here and read <file:Documentation/kbuild/modules.txt>.
  16. config USB_EMI26
  17. tristate "EMI 2|6 USB Audio interface support"
  18. ---help---
  19. This driver loads firmware to Emagic EMI 2|6 low latency USB
  20. Audio interface.
  21. After firmware load the device is handled with standard linux
  22. USB Audio driver.
  23. To compile this driver as a module, choose M here: the
  24. module will be called emi26.
  25. config USB_ADUTUX
  26. tristate "ADU devices from Ontrak Control Systems"
  27. help
  28. Say Y if you want to use an ADU device from Ontrak Control
  29. Systems.
  30. To compile this driver as a module, choose M here. The module
  31. will be called adutux.
  32. config USB_SEVSEG
  33. tristate "USB 7-Segment LED Display"
  34. help
  35. Say Y here if you have a USB 7-Segment Display by Delcom
  36. To compile this driver as a module, choose M here: the
  37. module will be called usbsevseg.
  38. config USB_RIO500
  39. tristate "USB Diamond Rio500 support"
  40. help
  41. Say Y here if you want to connect a USB Rio500 mp3 player to your
  42. computer's USB port. Please read <file:Documentation/usb/rio.txt>
  43. for more information.
  44. To compile this driver as a module, choose M here: the
  45. module will be called rio500.
  46. config USB_LEGOTOWER
  47. tristate "USB Lego Infrared Tower support"
  48. help
  49. Say Y here if you want to connect a USB Lego Infrared Tower to your
  50. computer's USB port.
  51. This code is also available as a module ( = code which can be
  52. inserted in and removed from the running kernel whenever you want).
  53. The module will be called legousbtower. If you want to compile it as
  54. a module, say M here and read
  55. <file:Documentation/kbuild/modules.txt>.
  56. config USB_LCD
  57. tristate "USB LCD driver support"
  58. help
  59. Say Y here if you want to connect an USBLCD to your computer's
  60. USB port. The USBLCD is a small USB interface board for
  61. alphanumeric LCD modules. See <http://www.usblcd.de/> for more
  62. information.
  63. To compile this driver as a module, choose M here: the
  64. module will be called usblcd.
  65. config USB_LED
  66. tristate "USB LED driver support"
  67. help
  68. Say Y here if you want to connect an USBLED device to your
  69. computer's USB port.
  70. To compile this driver as a module, choose M here: the
  71. module will be called usbled.
  72. config USB_CYPRESS_CY7C63
  73. tristate "Cypress CY7C63xxx USB driver support"
  74. help
  75. Say Y here if you want to connect a Cypress CY7C63xxx
  76. micro controller to your computer's USB port. Currently this
  77. driver supports the pre-programmed devices (incl. firmware)
  78. by AK Modul-Bus Computer GmbH.
  79. Please see: http://www.ak-modul-bus.de/stat/mikrocontroller.html
  80. To compile this driver as a module, choose M here: the
  81. module will be called cypress_cy7c63.
  82. config USB_CYTHERM
  83. tristate "Cypress USB thermometer driver support"
  84. help
  85. Say Y here if you want to connect a Cypress USB thermometer
  86. device to your computer's USB port. This device is also known
  87. as the Cypress USB Starter kit or demo board. The Elektor
  88. magazine published a modified version of this device in issue
  89. #291.
  90. To compile this driver as a module, choose M here: the
  91. module will be called cytherm.
  92. config USB_IDMOUSE
  93. tristate "Siemens ID USB Mouse Fingerprint sensor support"
  94. help
  95. Say Y here if you want to use the fingerprint sensor on
  96. the Siemens ID Mouse. There is also a Siemens ID Mouse
  97. _Professional_, which has not been tested with this driver,
  98. but uses the same sensor and may therefore work.
  99. This driver creates an entry "/dev/idmouseX" or "/dev/usb/idmouseX",
  100. which can be used by, e.g.,"cat /dev/idmouse0 > fingerprint.pnm".
  101. See also <http://www.fs.tum.de/~echtler/idmouse/>.
  102. config USB_FTDI_ELAN
  103. tristate "Elan PCMCIA CardBus Adapter USB Client"
  104. help
  105. ELAN's Uxxx series of adapters are USB to PCMCIA CardBus adapters.
  106. Currently only the U132 adapter is available.
  107. The U132 is specifically designed for CardBus PC cards that contain
  108. an OHCI host controller. Typical PC cards are the Orange Mobile 3G
  109. Option GlobeTrotter Fusion card. The U132 adapter will *NOT* work
  110. with PC cards that do not contain an OHCI controller. To use a U132
  111. adapter you will need this "ftdi-elan" module as well as the "u132-hcd"
  112. module which is a USB host controller driver that talks to the OHCI
  113. controller within CardBus card that are inserted in the U132 adapter.
  114. This driver has been tested with a CardBus OHCI USB adapter, and
  115. worked with a USB PEN Drive inserted into the first USB port of
  116. the PCCARD. A rather pointless thing to do, but useful for testing.
  117. See also the USB_U132_HCD entry "Elan U132 Adapter Host Controller"
  118. It is safe to say M here.
  119. config USB_APPLEDISPLAY
  120. tristate "Apple Cinema Display support"
  121. select BACKLIGHT_LCD_SUPPORT
  122. select BACKLIGHT_CLASS_DEVICE
  123. help
  124. Say Y here if you want to control the backlight of Apple Cinema
  125. Displays over USB. This driver provides a sysfs interface.
  126. source "drivers/usb/misc/sisusbvga/Kconfig"
  127. config USB_LD
  128. tristate "USB LD driver"
  129. help
  130. This driver is for generic USB devices that use interrupt transfers,
  131. like LD Didactic's USB devices.
  132. To compile this driver as a module, choose M here: the
  133. module will be called ldusb.
  134. config USB_TRANCEVIBRATOR
  135. tristate "PlayStation 2 Trance Vibrator driver support"
  136. help
  137. Say Y here if you want to connect a PlayStation 2 Trance Vibrator
  138. device to your computer's USB port.
  139. To compile this driver as a module, choose M here: the
  140. module will be called trancevibrator.
  141. config USB_IOWARRIOR
  142. tristate "IO Warrior driver support"
  143. help
  144. Say Y here if you want to support the IO Warrior devices from Code
  145. Mercenaries. This includes support for the following devices:
  146. IO Warrior 40
  147. IO Warrior 24
  148. IO Warrior 56
  149. IO Warrior 24 Power Vampire
  150. To compile this driver as a module, choose M here: the
  151. module will be called iowarrior.
  152. config USB_TEST
  153. tristate "USB testing driver"
  154. help
  155. This driver is for testing host controller software. It is used
  156. with specialized device firmware for regression and stress testing,
  157. to help prevent problems from cropping up with "real" drivers.
  158. See <http://www.linux-usb.org/usbtest/> for more information,
  159. including sample test device firmware and "how to use it".
  160. config USB_EHSET_TEST_FIXTURE
  161. tristate "USB EHSET Test Fixture driver"
  162. help
  163. Say Y here if you want to support the special test fixture device
  164. used for the USB-IF Embedded Host High-Speed Electrical Test procedure.
  165. When the test fixture is connected, it can enumerate as one of several
  166. VID/PID pairs. This driver then initiates a corresponding test mode on
  167. the downstream port to which the test fixture is attached.
  168. See <http://www.usb.org/developers/onthego/EHSET_v1.01.pdf> for more
  169. information.
  170. config USB_ISIGHTFW
  171. tristate "iSight firmware loading support"
  172. select FW_LOADER
  173. help
  174. This driver loads firmware for USB Apple iSight cameras, allowing
  175. them to be driven by the USB video class driver available at
  176. http://linux-uvc.berlios.de
  177. The firmware for this driver must be extracted from the MacOS
  178. driver beforehand. Tools for doing so are available at
  179. http://bersace03.free.fr
  180. config USB_YUREX
  181. tristate "USB YUREX driver support"
  182. help
  183. Say Y here if you want to connect a YUREX to your computer's
  184. USB port. The YUREX is a leg-shakes sensor. See
  185. <http://bbu.kayac.com/en/> for further information.
  186. This driver supports read/write of leg-shakes counter and
  187. fasync for the counter update via a device file /dev/yurex*.
  188. To compile this driver as a module, choose M here: the
  189. module will be called yurex.
  190. config USB_EZUSB_FX2
  191. tristate "Functions for loading firmware on EZUSB chips"
  192. help
  193. Say Y here if you need EZUSB device support.
  194. (Cypress FX/FX2/FX2LP microcontrollers)
  195. config USB_HSIC_USB3503
  196. tristate "USB3503 HSIC to USB20 Driver"
  197. depends on I2C
  198. select REGMAP_I2C
  199. help
  200. This option enables support for SMSC USB3503 HSIC to USB 2.0 Driver.
  201. config USB_LINK_LAYER_TEST
  202. tristate "USB Link Layer Test driver"
  203. help
  204. This driver is for generating specific traffic for Super Speed Link
  205. Layer Test Device. Say Y only when you want to conduct USB Super Speed
  206. Link Layer Test for host controllers.
  207. config USB_CHAOSKEY
  208. tristate "ChaosKey random number generator driver support"
  209. depends on HW_RANDOM
  210. help
  211. Say Y here if you want to connect an AltusMetrum ChaosKey to
  212. your computer's USB port. The ChaosKey is a hardware random
  213. number generator which hooks into the kernel entropy pool to
  214. ensure a large supply of entropy for /dev/random and
  215. /dev/urandom and also provides direct access via /dev/chaoskeyX
  216. To compile this driver as a module, choose M here: the
  217. module will be called chaoskey.