Kconfig 11 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313
  1. # SPDX-License-Identifier: GPL-2.0
  2. #
  3. # USB Miscellaneous driver configuration
  4. #
  5. comment "USB Miscellaneous drivers"
  6. config USB_EMI62
  7. tristate "EMI 6|2m USB Audio interface support"
  8. help
  9. This driver loads firmware to Emagic EMI 6|2m low latency USB
  10. Audio and Midi interface.
  11. After firmware load the device is handled with standard linux
  12. USB Audio driver.
  13. This code is also available as a module ( = code which can be
  14. inserted in and removed from the running kernel whenever you want).
  15. The module will be called audio. If you want to compile it as a
  16. module, say M here and read <file:Documentation/kbuild/modules.rst>.
  17. config USB_EMI26
  18. tristate "EMI 2|6 USB Audio interface support"
  19. help
  20. This driver loads firmware to Emagic EMI 2|6 low latency USB
  21. Audio interface.
  22. After firmware load the device is handled with standard linux
  23. USB Audio driver.
  24. To compile this driver as a module, choose M here: the
  25. module will be called emi26.
  26. config USB_ADUTUX
  27. tristate "ADU devices from Ontrak Control Systems"
  28. help
  29. Say Y if you want to use an ADU device from Ontrak Control
  30. Systems.
  31. To compile this driver as a module, choose M here. The module
  32. will be called adutux.
  33. config USB_SEVSEG
  34. tristate "USB 7-Segment LED Display"
  35. help
  36. Say Y here if you have a USB 7-Segment Display by Delcom
  37. To compile this driver as a module, choose M here: the
  38. module will be called usbsevseg.
  39. config USB_LEGOTOWER
  40. tristate "USB Lego Infrared Tower support"
  41. help
  42. Say Y here if you want to connect a USB Lego Infrared Tower to your
  43. computer's USB port.
  44. This code is also available as a module ( = code which can be
  45. inserted in and removed from the running kernel whenever you want).
  46. The module will be called legousbtower. If you want to compile it as
  47. a module, say M here and read
  48. <file:Documentation/kbuild/modules.rst>.
  49. config USB_LCD
  50. tristate "USB LCD driver support"
  51. help
  52. Say Y here if you want to connect an USBLCD to your computer's
  53. USB port. The USBLCD is a small USB interface board for
  54. alphanumeric LCD modules. See <http://www.usblcd.de/> for more
  55. information.
  56. To compile this driver as a module, choose M here: the
  57. module will be called usblcd.
  58. config USB_CYPRESS_CY7C63
  59. tristate "Cypress CY7C63xxx USB driver support"
  60. help
  61. Say Y here if you want to connect a Cypress CY7C63xxx
  62. micro controller to your computer's USB port. Currently this
  63. driver supports the pre-programmed devices (incl. firmware)
  64. by AK Modul-Bus Computer GmbH.
  65. Please see: https://www.ak-modul-bus.de/stat/mikrocontroller.html
  66. To compile this driver as a module, choose M here: the
  67. module will be called cypress_cy7c63.
  68. config USB_CYTHERM
  69. tristate "Cypress USB thermometer driver support"
  70. help
  71. Say Y here if you want to connect a Cypress USB thermometer
  72. device to your computer's USB port. This device is also known
  73. as the Cypress USB Starter kit or demo board. The Elektor
  74. magazine published a modified version of this device in issue
  75. #291.
  76. To compile this driver as a module, choose M here: the
  77. module will be called cytherm.
  78. config USB_IDMOUSE
  79. tristate "Siemens ID USB Mouse Fingerprint sensor support"
  80. help
  81. Say Y here if you want to use the fingerprint sensor on
  82. the Siemens ID Mouse. There is also a Siemens ID Mouse
  83. _Professional_, which has not been tested with this driver,
  84. but uses the same sensor and may therefore work.
  85. This driver creates an entry "/dev/idmouseX" or "/dev/usb/idmouseX",
  86. which can be used by, e.g.,"cat /dev/idmouse0 > fingerprint.pnm".
  87. See also <https://www.fs.tum.de/~echtler/idmouse/>.
  88. config USB_FTDI_ELAN
  89. tristate "Elan PCMCIA CardBus Adapter USB Client"
  90. help
  91. ELAN's Uxxx series of adapters are USB to PCMCIA CardBus adapters.
  92. Currently only the U132 adapter is available.
  93. The U132 is specifically designed for CardBus PC cards that contain
  94. an OHCI host controller. Typical PC cards are the Orange Mobile 3G
  95. Option GlobeTrotter Fusion card. The U132 adapter will *NOT* work
  96. with PC cards that do not contain an OHCI controller. To use a U132
  97. adapter you will need this "ftdi-elan" module as well as the "u132-hcd"
  98. module which is a USB host controller driver that talks to the OHCI
  99. controller within CardBus card that are inserted in the U132 adapter.
  100. This driver has been tested with a CardBus OHCI USB adapter, and
  101. worked with a USB PEN Drive inserted into the first USB port of
  102. the PCCARD. A rather pointless thing to do, but useful for testing.
  103. See also the USB_U132_HCD entry "Elan U132 Adapter Host Controller"
  104. It is safe to say M here.
  105. config USB_APPLEDISPLAY
  106. tristate "Apple Cinema Display 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. config USB_QCOM_EUD
  112. tristate "QCOM Embedded USB Debugger(EUD) Driver"
  113. depends on ARCH_QCOM || COMPILE_TEST
  114. select USB_ROLE_SWITCH
  115. help
  116. This module enables support for Qualcomm Technologies, Inc.
  117. Embedded USB Debugger (EUD). The EUD is a control peripheral
  118. which reports VBUS attach/detach events and has USB-based
  119. debug and trace capabilities. On selecting m, the module name
  120. that is built is qcom_eud.ko
  121. config APPLE_MFI_FASTCHARGE
  122. tristate "Fast charge control for iOS devices"
  123. select POWER_SUPPLY
  124. help
  125. Say Y here if you want to control whether iOS devices will
  126. fast charge from the USB interface, as implemented in "MFi"
  127. chargers.
  128. It is safe to say M here.
  129. source "drivers/usb/misc/sisusbvga/Kconfig"
  130. config USB_LD
  131. tristate "USB LD driver"
  132. help
  133. This driver is for generic USB devices that use interrupt transfers,
  134. like LD Didactic's USB devices.
  135. To compile this driver as a module, choose M here: the
  136. module will be called ldusb.
  137. config USB_TRANCEVIBRATOR
  138. tristate "PlayStation 2 Trance Vibrator driver support"
  139. help
  140. Say Y here if you want to connect a PlayStation 2 Trance Vibrator
  141. device to your computer's USB port.
  142. To compile this driver as a module, choose M here: the
  143. module will be called trancevibrator.
  144. config USB_IOWARRIOR
  145. tristate "IO Warrior driver support"
  146. help
  147. Say Y here if you want to support the IO Warrior devices from Code
  148. Mercenaries. This includes support for the following devices:
  149. IO Warrior 40
  150. IO Warrior 24
  151. IO Warrior 56
  152. IO Warrior 24 Power Vampire
  153. To compile this driver as a module, choose M here: the
  154. module will be called iowarrior.
  155. config USB_TEST
  156. tristate "USB testing driver"
  157. help
  158. This driver is for testing host controller software. It is used
  159. with specialized device firmware for regression and stress testing,
  160. to help prevent problems from cropping up with "real" drivers.
  161. See <http://www.linux-usb.org/usbtest/> for more information,
  162. including sample test device firmware and "how to use it".
  163. config USB_EHSET_TEST_FIXTURE
  164. tristate "USB EHSET Test Fixture driver"
  165. help
  166. Say Y here if you want to support the special test fixture device
  167. used for the USB-IF Embedded Host High-Speed Electrical Test procedure.
  168. When the test fixture is connected, it can enumerate as one of several
  169. VID/PID pairs. This driver then initiates a corresponding test mode on
  170. the downstream port to which the test fixture is attached.
  171. See <http://www.usb.org/developers/onthego/EHSET_v1.01.pdf> for more
  172. information.
  173. config USB_ISIGHTFW
  174. tristate "iSight firmware loading support"
  175. select FW_LOADER
  176. help
  177. This driver loads firmware for USB Apple iSight cameras, allowing
  178. them to be driven by the USB video class driver available at
  179. http://linux-uvc.berlios.de
  180. The firmware for this driver must be extracted from the MacOS
  181. driver beforehand. Tools for doing so are available at
  182. http://bersace03.free.fr
  183. config USB_YUREX
  184. tristate "USB YUREX driver support"
  185. help
  186. Say Y here if you want to connect a YUREX to your computer's
  187. USB port. The YUREX is a leg-shakes sensor. See
  188. <http://bbu.kayac.com/en/> for further information.
  189. This driver supports read/write of leg-shakes counter and
  190. fasync for the counter update via a device file /dev/yurex*.
  191. To compile this driver as a module, choose M here: the
  192. module will be called yurex.
  193. config USB_EZUSB_FX2
  194. tristate "Functions for loading firmware on EZUSB chips"
  195. help
  196. Say Y here if you need EZUSB device support.
  197. (Cypress FX/FX2/FX2LP microcontrollers)
  198. config USB_HUB_USB251XB
  199. tristate "USB251XB Hub Controller Configuration Driver"
  200. depends on I2C
  201. help
  202. This option enables support for configuration via SMBus of the
  203. Microchip USB251x/xBi USB 2.0 Hub Controller series. Configuration
  204. parameters may be set in devicetree or platform data.
  205. Say Y or M here if you need to configure such a device via SMBus.
  206. config USB_HSIC_USB3503
  207. tristate "USB3503 HSIC to USB20 Driver"
  208. depends on I2C
  209. select REGMAP_I2C
  210. help
  211. This option enables support for SMSC USB3503 HSIC to USB 2.0 Driver.
  212. config USB_HSIC_USB4604
  213. tristate "USB4604 HSIC to USB20 Driver"
  214. depends on I2C
  215. help
  216. This option enables support for SMSC USB4604 HSIC to USB 2.0 Driver.
  217. config USB_LINK_LAYER_TEST
  218. tristate "USB Link Layer Test driver"
  219. help
  220. This driver is for generating specific traffic for Super Speed Link
  221. Layer Test Device. Say Y only when you want to conduct USB Super Speed
  222. Link Layer Test for host controllers.
  223. config USB_CHAOSKEY
  224. tristate "ChaosKey random number generator driver support"
  225. depends on HW_RANDOM
  226. help
  227. Say Y here if you want to connect an AltusMetrum ChaosKey or
  228. Araneus Alea I to your computer's USB port. These devices
  229. are hardware random number generators which hook into the
  230. kernel entropy pool to ensure a large supply of entropy for
  231. /dev/random and /dev/urandom and also provides direct access
  232. via /dev/chaoskeyX
  233. To compile this driver as a module, choose M here: the
  234. module will be called chaoskey.
  235. config BRCM_USB_PINMAP
  236. tristate "Broadcom pinmap driver support"
  237. depends on (ARCH_BRCMSTB && PHY_BRCM_USB) || COMPILE_TEST
  238. default ARCH_BRCMSTB && PHY_BRCM_USB
  239. help
  240. This option enables support for remapping some USB external
  241. signals, which are typically on dedicated pins on the chip,
  242. to any gpio.
  243. config USB_ONBOARD_HUB
  244. tristate "Onboard USB hub support"
  245. depends on OF || COMPILE_TEST
  246. help
  247. Say Y here if you want to support discrete onboard USB hubs that
  248. don't require an additional control bus for initialization, but
  249. need some non-trivial form of initialization, such as enabling a
  250. power regulator. An example for such a hub is the Realtek
  251. RTS5411.
  252. This driver can be used as a module but its state (module vs
  253. builtin) must match the state of the USB subsystem. Enabling
  254. this config will enable the driver and it will automatically
  255. match the state of the USB subsystem. If this driver is a
  256. module it will be called onboard_usb_hub.