Kconfig 12 KB

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