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