Kconfig 10 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295
  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_CYPRESS_CY7C63
  66. tristate "Cypress CY7C63xxx USB driver support"
  67. help
  68. Say Y here if you want to connect a Cypress CY7C63xxx
  69. micro controller to your computer's USB port. Currently this
  70. driver supports the pre-programmed devices (incl. firmware)
  71. by AK Modul-Bus Computer GmbH.
  72. Please see: http://www.ak-modul-bus.de/stat/mikrocontroller.html
  73. To compile this driver as a module, choose M here: the
  74. module will be called cypress_cy7c63.
  75. config USB_CYTHERM
  76. tristate "Cypress USB thermometer driver support"
  77. help
  78. Say Y here if you want to connect a Cypress USB thermometer
  79. device to your computer's USB port. This device is also known
  80. as the Cypress USB Starter kit or demo board. The Elektor
  81. magazine published a modified version of this device in issue
  82. #291.
  83. To compile this driver as a module, choose M here: the
  84. module will be called cytherm.
  85. config USB_IDMOUSE
  86. tristate "Siemens ID USB Mouse Fingerprint sensor support"
  87. help
  88. Say Y here if you want to use the fingerprint sensor on
  89. the Siemens ID Mouse. There is also a Siemens ID Mouse
  90. _Professional_, which has not been tested with this driver,
  91. but uses the same sensor and may therefore work.
  92. This driver creates an entry "/dev/idmouseX" or "/dev/usb/idmouseX",
  93. which can be used by, e.g.,"cat /dev/idmouse0 > fingerprint.pnm".
  94. See also <http://www.fs.tum.de/~echtler/idmouse/>.
  95. config USB_FTDI_ELAN
  96. tristate "Elan PCMCIA CardBus Adapter USB Client"
  97. help
  98. ELAN's Uxxx series of adapters are USB to PCMCIA CardBus adapters.
  99. Currently only the U132 adapter is available.
  100. The U132 is specifically designed for CardBus PC cards that contain
  101. an OHCI host controller. Typical PC cards are the Orange Mobile 3G
  102. Option GlobeTrotter Fusion card. The U132 adapter will *NOT* work
  103. with PC cards that do not contain an OHCI controller. To use a U132
  104. adapter you will need this "ftdi-elan" module as well as the "u132-hcd"
  105. module which is a USB host controller driver that talks to the OHCI
  106. controller within CardBus card that are inserted in the U132 adapter.
  107. This driver has been tested with a CardBus OHCI USB adapter, and
  108. worked with a USB PEN Drive inserted into the first USB port of
  109. the PCCARD. A rather pointless thing to do, but useful for testing.
  110. See also the USB_U132_HCD entry "Elan U132 Adapter Host Controller"
  111. It is safe to say M here.
  112. config USB_APPLEDISPLAY
  113. tristate "Apple Cinema Display support"
  114. select BACKLIGHT_LCD_SUPPORT
  115. select BACKLIGHT_CLASS_DEVICE
  116. help
  117. Say Y here if you want to control the backlight of Apple Cinema
  118. Displays over USB. This driver provides a sysfs interface.
  119. source "drivers/usb/misc/sisusbvga/Kconfig"
  120. config USB_LD
  121. tristate "USB LD driver"
  122. help
  123. This driver is for generic USB devices that use interrupt transfers,
  124. like LD Didactic's USB devices.
  125. To compile this driver as a module, choose M here: the
  126. module will be called ldusb.
  127. config USB_TRANCEVIBRATOR
  128. tristate "PlayStation 2 Trance Vibrator driver support"
  129. help
  130. Say Y here if you want to connect a PlayStation 2 Trance Vibrator
  131. device to your computer's USB port.
  132. To compile this driver as a module, choose M here: the
  133. module will be called trancevibrator.
  134. config USB_IOWARRIOR
  135. tristate "IO Warrior driver support"
  136. help
  137. Say Y here if you want to support the IO Warrior devices from Code
  138. Mercenaries. This includes support for the following devices:
  139. IO Warrior 40
  140. IO Warrior 24
  141. IO Warrior 56
  142. IO Warrior 24 Power Vampire
  143. To compile this driver as a module, choose M here: the
  144. module will be called iowarrior.
  145. config USB_TEST
  146. tristate "USB testing driver"
  147. help
  148. This driver is for testing host controller software. It is used
  149. with specialized device firmware for regression and stress testing,
  150. to help prevent problems from cropping up with "real" drivers.
  151. See <http://www.linux-usb.org/usbtest/> for more information,
  152. including sample test device firmware and "how to use it".
  153. config USB_EHSET_TEST_FIXTURE
  154. tristate "USB EHSET Test Fixture driver"
  155. help
  156. Say Y here if you want to support the special test fixture device
  157. used for the USB-IF Embedded Host High-Speed Electrical Test procedure.
  158. When the test fixture is connected, it can enumerate as one of several
  159. VID/PID pairs. This driver then initiates a corresponding test mode on
  160. the downstream port to which the test fixture is attached.
  161. See <http://www.usb.org/developers/onthego/EHSET_v1.01.pdf> for more
  162. information.
  163. config USB_ISIGHTFW
  164. tristate "iSight firmware loading support"
  165. select FW_LOADER
  166. help
  167. This driver loads firmware for USB Apple iSight cameras, allowing
  168. them to be driven by the USB video class driver available at
  169. http://linux-uvc.berlios.de
  170. The firmware for this driver must be extracted from the MacOS
  171. driver beforehand. Tools for doing so are available at
  172. http://bersace03.free.fr
  173. config USB_YUREX
  174. tristate "USB YUREX driver support"
  175. help
  176. Say Y here if you want to connect a YUREX to your computer's
  177. USB port. The YUREX is a leg-shakes sensor. See
  178. <http://bbu.kayac.com/en/> for further information.
  179. This driver supports read/write of leg-shakes counter and
  180. fasync for the counter update via a device file /dev/yurex*.
  181. To compile this driver as a module, choose M here: the
  182. module will be called yurex.
  183. config USB_EZUSB_FX2
  184. tristate "Functions for loading firmware on EZUSB chips"
  185. help
  186. Say Y here if you need EZUSB device support.
  187. (Cypress FX/FX2/FX2LP microcontrollers)
  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.
  217. config UCSI
  218. tristate "USB Type-C Connector System Software Interface driver"
  219. depends on ACPI
  220. help
  221. UCSI driver is meant to be used as a convenience tool for desktop and
  222. server systems that are not equipped to handle USB in device mode. It
  223. will always select USB host role for the USB Type-C ports on systems
  224. that provide UCSI interface.
  225. USB Type-C Connector System Software Interface (UCSI) is a
  226. specification for an interface that allows the Operating System to
  227. control the USB Type-C ports on a system. Things the need controlling
  228. include the USB Data Role (host or device), and when USB Power
  229. Delivery is supported, the Power Role (source or sink). With USB
  230. Type-C connectors, when two dual role capable devices are attached
  231. together, the data role is selected randomly. Therefore it is
  232. important to give the OS a way to select the role. Otherwise the user
  233. would have to unplug and replug in order in order to attempt to swap
  234. the data and power roles.
  235. The UCSI specification can be downloaded from:
  236. http://www.intel.com/content/www/us/en/io/universal-serial-bus/usb-type-c-ucsi-spec.html
  237. To compile the driver as a module, choose M here: the module will be
  238. called ucsi.