1 # SPDX-License-Identifier: GPL-2.0
3 # USB Miscellaneous driver configuration
5 comment "USB Miscellaneous drivers"
8 tristate "EMI 6|2m USB Audio interface support"
10 This driver loads firmware to Emagic EMI 6|2m low latency USB
11 Audio and Midi interface.
13 After firmware load the device is handled with standard linux
16 This code is also available as a module ( = code which can be
17 inserted in and removed from the running kernel whenever you want).
18 The module will be called audio. If you want to compile it as a
19 module, say M here and read <file:Documentation/kbuild/modules.rst>.
22 tristate "EMI 2|6 USB Audio interface support"
24 This driver loads firmware to Emagic EMI 2|6 low latency USB
27 After firmware load the device is handled with standard linux
30 To compile this driver as a module, choose M here: the
31 module will be called emi26.
34 tristate "ADU devices from Ontrak Control Systems"
36 Say Y if you want to use an ADU device from Ontrak Control
39 To compile this driver as a module, choose M here. The module
40 will be called adutux.
43 tristate "USB 7-Segment LED Display"
45 Say Y here if you have a USB 7-Segment Display by Delcom
47 To compile this driver as a module, choose M here: the
48 module will be called usbsevseg.
51 tristate "USB Lego Infrared Tower support"
53 Say Y here if you want to connect a USB Lego Infrared Tower to your
56 This code is also available as a module ( = code which can be
57 inserted in and removed from the running kernel whenever you want).
58 The module will be called legousbtower. If you want to compile it as
59 a module, say M here and read
60 <file:Documentation/kbuild/modules.rst>.
63 tristate "USB LCD driver support"
65 Say Y here if you want to connect an USBLCD to your computer's
66 USB port. The USBLCD is a small USB interface board for
67 alphanumeric LCD modules. See <http://www.usblcd.de/> for more
70 To compile this driver as a module, choose M here: the
71 module will be called usblcd.
73 config USB_CYPRESS_CY7C63
74 tristate "Cypress CY7C63xxx USB driver support"
76 Say Y here if you want to connect a Cypress CY7C63xxx
77 micro controller to your computer's USB port. Currently this
78 driver supports the pre-programmed devices (incl. firmware)
79 by AK Modul-Bus Computer GmbH.
81 Please see: https://www.ak-modul-bus.de/stat/mikrocontroller.html
83 To compile this driver as a module, choose M here: the
84 module will be called cypress_cy7c63.
87 tristate "Cypress USB thermometer driver support"
89 Say Y here if you want to connect a Cypress USB thermometer
90 device to your computer's USB port. This device is also known
91 as the Cypress USB Starter kit or demo board. The Elektor
92 magazine published a modified version of this device in issue
95 To compile this driver as a module, choose M here: the
96 module will be called cytherm.
99 tristate "Siemens ID USB Mouse Fingerprint sensor support"
101 Say Y here if you want to use the fingerprint sensor on
102 the Siemens ID Mouse. There is also a Siemens ID Mouse
103 _Professional_, which has not been tested with this driver,
104 but uses the same sensor and may therefore work.
106 This driver creates an entry "/dev/idmouseX" or "/dev/usb/idmouseX",
107 which can be used by, e.g.,"cat /dev/idmouse0 > fingerprint.pnm".
109 See also <https://www.fs.tum.de/~echtler/idmouse/>.
112 tristate "Elan PCMCIA CardBus Adapter USB Client"
114 ELAN's Uxxx series of adapters are USB to PCMCIA CardBus adapters.
115 Currently only the U132 adapter is available.
117 The U132 is specifically designed for CardBus PC cards that contain
118 an OHCI host controller. Typical PC cards are the Orange Mobile 3G
119 Option GlobeTrotter Fusion card. The U132 adapter will *NOT* work
120 with PC cards that do not contain an OHCI controller. To use a U132
121 adapter you will need this "ftdi-elan" module as well as the "u132-hcd"
122 module which is a USB host controller driver that talks to the OHCI
123 controller within CardBus card that are inserted in the U132 adapter.
125 This driver has been tested with a CardBus OHCI USB adapter, and
126 worked with a USB PEN Drive inserted into the first USB port of
127 the PCCARD. A rather pointless thing to do, but useful for testing.
129 See also the USB_U132_HCD entry "Elan U132 Adapter Host Controller"
131 It is safe to say M here.
133 config USB_APPLEDISPLAY
134 tristate "Apple Cinema Display support"
135 select BACKLIGHT_CLASS_DEVICE
137 Say Y here if you want to control the backlight of Apple Cinema
138 Displays over USB. This driver provides a sysfs interface.
141 tristate "QCOM Embedded USB Debugger(EUD) Driver"
142 depends on ARCH_QCOM || COMPILE_TEST
143 select USB_ROLE_SWITCH
145 This module enables support for Qualcomm Technologies, Inc.
146 Embedded USB Debugger (EUD). The EUD is a control peripheral
147 which reports VBUS attach/detach events and has USB-based
148 debug and trace capabilities. On selecting m, the module name
149 that is built is qcom_eud.ko
151 config APPLE_MFI_FASTCHARGE
152 tristate "Fast charge control for iOS devices"
155 Say Y here if you want to control whether iOS devices will
156 fast charge from the USB interface, as implemented in "MFi"
159 It is safe to say M here.
161 source "drivers/usb/misc/sisusbvga/Kconfig"
164 tristate "USB LD driver"
166 This driver is for generic USB devices that use interrupt transfers,
167 like LD Didactic's USB devices.
169 To compile this driver as a module, choose M here: the
170 module will be called ldusb.
172 config USB_TRANCEVIBRATOR
173 tristate "PlayStation 2 Trance Vibrator driver support"
175 Say Y here if you want to connect a PlayStation 2 Trance Vibrator
176 device to your computer's USB port.
178 To compile this driver as a module, choose M here: the
179 module will be called trancevibrator.
182 tristate "IO Warrior driver support"
184 Say Y here if you want to support the IO Warrior devices from Code
185 Mercenaries. This includes support for the following devices:
189 IO Warrior 24 Power Vampire
191 To compile this driver as a module, choose M here: the
192 module will be called iowarrior.
195 tristate "USB testing driver"
197 This driver is for testing host controller software. It is used
198 with specialized device firmware for regression and stress testing,
199 to help prevent problems from cropping up with "real" drivers.
201 See <http://www.linux-usb.org/usbtest/> for more information,
202 including sample test device firmware and "how to use it".
204 config USB_EHSET_TEST_FIXTURE
205 tristate "USB EHSET Test Fixture driver"
207 Say Y here if you want to support the special test fixture device
208 used for the USB-IF Embedded Host High-Speed Electrical Test procedure.
210 When the test fixture is connected, it can enumerate as one of several
211 VID/PID pairs. This driver then initiates a corresponding test mode on
212 the downstream port to which the test fixture is attached.
214 See <http://www.usb.org/developers/onthego/EHSET_v1.01.pdf> for more
218 tristate "iSight firmware loading support"
221 This driver loads firmware for USB Apple iSight cameras, allowing
222 them to be driven by the USB video class driver available at
223 http://linux-uvc.berlios.de
225 The firmware for this driver must be extracted from the MacOS
226 driver beforehand. Tools for doing so are available at
227 http://bersace03.free.fr
230 tristate "USB YUREX driver support"
232 Say Y here if you want to connect a YUREX to your computer's
233 USB port. The YUREX is a leg-shakes sensor. See
234 <http://bbu.kayac.com/en/> for further information.
235 This driver supports read/write of leg-shakes counter and
236 fasync for the counter update via a device file /dev/yurex*.
238 To compile this driver as a module, choose M here: the
239 module will be called yurex.
242 tristate "Functions for loading firmware on EZUSB chips"
244 Say Y here if you need EZUSB device support.
245 (Cypress FX/FX2/FX2LP microcontrollers)
247 config USB_HUB_USB251XB
248 tristate "USB251XB Hub Controller Configuration Driver"
251 This option enables support for configuration via SMBus of the
252 Microchip USB251x/xBi USB 2.0 Hub Controller series. Configuration
253 parameters may be set in devicetree or platform data.
254 Say Y or M here if you need to configure such a device via SMBus.
256 config USB_HSIC_USB3503
257 tristate "USB3503 HSIC to USB20 Driver"
261 This option enables support for SMSC USB3503 HSIC to USB 2.0 Driver.
263 config USB_HSIC_USB4604
264 tristate "USB4604 HSIC to USB20 Driver"
267 This option enables support for SMSC USB4604 HSIC to USB 2.0 Driver.
269 config USB_LINK_LAYER_TEST
270 tristate "USB Link Layer Test driver"
272 This driver is for generating specific traffic for Super Speed Link
273 Layer Test Device. Say Y only when you want to conduct USB Super Speed
274 Link Layer Test for host controllers.
277 tristate "ChaosKey random number generator driver support"
280 Say Y here if you want to connect an AltusMetrum ChaosKey or
281 Araneus Alea I to your computer's USB port. These devices
282 are hardware random number generators which hook into the
283 kernel entropy pool to ensure a large supply of entropy for
284 /dev/random and /dev/urandom and also provides direct access
287 To compile this driver as a module, choose M here: the
288 module will be called chaoskey.
290 config BRCM_USB_PINMAP
291 tristate "Broadcom pinmap driver support"
292 depends on (ARCH_BRCMSTB && PHY_BRCM_USB) || COMPILE_TEST
293 default ARCH_BRCMSTB && PHY_BRCM_USB
295 This option enables support for remapping some USB external
296 signals, which are typically on dedicated pins on the chip,
299 config USB_ONBOARD_HUB
300 tristate "Onboard USB hub support"
301 depends on OF || COMPILE_TEST
303 Say Y here if you want to support discrete onboard USB hubs that
304 don't require an additional control bus for initialization, but
305 need some non-trivial form of initialization, such as enabling a
306 power regulator. An example for such a hub is the Realtek
309 This driver can be used as a module but its state (module vs
310 builtin) must match the state of the USB subsystem. Enabling
311 this config will enable the driver and it will automatically
312 match the state of the USB subsystem. If this driver is a
313 module it will be called onboard_usb_hub.