Kconfig 9.2 KB

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