1# SPDX-License-Identifier: GPL-2.0 2# 3# USB Miscellaneous driver configuration 4# 5comment "USB Miscellaneous drivers" 6 7config USB_EMI62 8 tristate "EMI 6|2m USB Audio interface support" 9 ---help--- 10 This driver loads firmware to Emagic EMI 6|2m low latency USB 11 Audio and Midi interface. 12 13 After firmware load the device is handled with standard linux 14 USB Audio driver. 15 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>. 20 21config USB_EMI26 22 tristate "EMI 2|6 USB Audio interface support" 23 ---help--- 24 This driver loads firmware to Emagic EMI 2|6 low latency USB 25 Audio interface. 26 27 After firmware load the device is handled with standard linux 28 USB Audio driver. 29 30 To compile this driver as a module, choose M here: the 31 module will be called emi26. 32 33config USB_ADUTUX 34 tristate "ADU devices from Ontrak Control Systems" 35 help 36 Say Y if you want to use an ADU device from Ontrak Control 37 Systems. 38 39 To compile this driver as a module, choose M here. The module 40 will be called adutux. 41 42config USB_SEVSEG 43 tristate "USB 7-Segment LED Display" 44 help 45 Say Y here if you have a USB 7-Segment Display by Delcom 46 47 To compile this driver as a module, choose M here: the 48 module will be called usbsevseg. 49 50config USB_LEGOTOWER 51 tristate "USB Lego Infrared Tower support" 52 help 53 Say Y here if you want to connect a USB Lego Infrared Tower to your 54 computer's USB port. 55 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>. 61 62config USB_LCD 63 tristate "USB LCD driver support" 64 help 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 68 information. 69 70 To compile this driver as a module, choose M here: the 71 module will be called usblcd. 72 73config USB_CYPRESS_CY7C63 74 tristate "Cypress CY7C63xxx USB driver support" 75 help 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. 80 81 Please see: http://www.ak-modul-bus.de/stat/mikrocontroller.html 82 83 To compile this driver as a module, choose M here: the 84 module will be called cypress_cy7c63. 85 86config USB_CYTHERM 87 tristate "Cypress USB thermometer driver support" 88 help 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 93 #291. 94 95 To compile this driver as a module, choose M here: the 96 module will be called cytherm. 97 98config USB_IDMOUSE 99 tristate "Siemens ID USB Mouse Fingerprint sensor support" 100 help 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. 105 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". 108 109 See also <http://www.fs.tum.de/~echtler/idmouse/>. 110 111config USB_FTDI_ELAN 112 tristate "Elan PCMCIA CardBus Adapter USB Client" 113 help 114 ELAN's Uxxx series of adapters are USB to PCMCIA CardBus adapters. 115 Currently only the U132 adapter is available. 116 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. 124 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. 128 129 See also the USB_U132_HCD entry "Elan U132 Adapter Host Controller" 130 131 It is safe to say M here. 132 133config USB_APPLEDISPLAY 134 tristate "Apple Cinema Display support" 135 select BACKLIGHT_CLASS_DEVICE 136 help 137 Say Y here if you want to control the backlight of Apple Cinema 138 Displays over USB. This driver provides a sysfs interface. 139 140source "drivers/usb/misc/sisusbvga/Kconfig" 141 142config USB_LD 143 tristate "USB LD driver" 144 help 145 This driver is for generic USB devices that use interrupt transfers, 146 like LD Didactic's USB devices. 147 148 To compile this driver as a module, choose M here: the 149 module will be called ldusb. 150 151config USB_TRANCEVIBRATOR 152 tristate "PlayStation 2 Trance Vibrator driver support" 153 help 154 Say Y here if you want to connect a PlayStation 2 Trance Vibrator 155 device to your computer's USB port. 156 157 To compile this driver as a module, choose M here: the 158 module will be called trancevibrator. 159 160config USB_IOWARRIOR 161 tristate "IO Warrior driver support" 162 help 163 Say Y here if you want to support the IO Warrior devices from Code 164 Mercenaries. This includes support for the following devices: 165 IO Warrior 40 166 IO Warrior 24 167 IO Warrior 56 168 IO Warrior 24 Power Vampire 169 170 To compile this driver as a module, choose M here: the 171 module will be called iowarrior. 172 173config USB_TEST 174 tristate "USB testing driver" 175 help 176 This driver is for testing host controller software. It is used 177 with specialized device firmware for regression and stress testing, 178 to help prevent problems from cropping up with "real" drivers. 179 180 See <http://www.linux-usb.org/usbtest/> for more information, 181 including sample test device firmware and "how to use it". 182 183config USB_EHSET_TEST_FIXTURE 184 tristate "USB EHSET Test Fixture driver" 185 help 186 Say Y here if you want to support the special test fixture device 187 used for the USB-IF Embedded Host High-Speed Electrical Test procedure. 188 189 When the test fixture is connected, it can enumerate as one of several 190 VID/PID pairs. This driver then initiates a corresponding test mode on 191 the downstream port to which the test fixture is attached. 192 193 See <http://www.usb.org/developers/onthego/EHSET_v1.01.pdf> for more 194 information. 195 196config USB_ISIGHTFW 197 tristate "iSight firmware loading support" 198 select FW_LOADER 199 help 200 This driver loads firmware for USB Apple iSight cameras, allowing 201 them to be driven by the USB video class driver available at 202 http://linux-uvc.berlios.de 203 204 The firmware for this driver must be extracted from the MacOS 205 driver beforehand. Tools for doing so are available at 206 http://bersace03.free.fr 207 208config USB_YUREX 209 tristate "USB YUREX driver support" 210 help 211 Say Y here if you want to connect a YUREX to your computer's 212 USB port. The YUREX is a leg-shakes sensor. See 213 <http://bbu.kayac.com/en/> for further information. 214 This driver supports read/write of leg-shakes counter and 215 fasync for the counter update via a device file /dev/yurex*. 216 217 To compile this driver as a module, choose M here: the 218 module will be called yurex. 219 220config USB_EZUSB_FX2 221 tristate "Functions for loading firmware on EZUSB chips" 222 help 223 Say Y here if you need EZUSB device support. 224 (Cypress FX/FX2/FX2LP microcontrollers) 225 226config USB_HUB_USB251XB 227 tristate "USB251XB Hub Controller Configuration Driver" 228 depends on I2C 229 help 230 This option enables support for configuration via SMBus of the 231 Microchip USB251x/xBi USB 2.0 Hub Controller series. Configuration 232 parameters may be set in devicetree or platform data. 233 Say Y or M here if you need to configure such a device via SMBus. 234 235config USB_HSIC_USB3503 236 tristate "USB3503 HSIC to USB20 Driver" 237 depends on I2C 238 select REGMAP_I2C 239 help 240 This option enables support for SMSC USB3503 HSIC to USB 2.0 Driver. 241 242config USB_HSIC_USB4604 243 tristate "USB4604 HSIC to USB20 Driver" 244 depends on I2C 245 help 246 This option enables support for SMSC USB4604 HSIC to USB 2.0 Driver. 247 248config USB_LINK_LAYER_TEST 249 tristate "USB Link Layer Test driver" 250 help 251 This driver is for generating specific traffic for Super Speed Link 252 Layer Test Device. Say Y only when you want to conduct USB Super Speed 253 Link Layer Test for host controllers. 254 255config USB_CHAOSKEY 256 tristate "ChaosKey random number generator driver support" 257 depends on HW_RANDOM 258 help 259 Say Y here if you want to connect an AltusMetrum ChaosKey or 260 Araneus Alea I to your computer's USB port. These devices 261 are hardware random number generators which hook into the 262 kernel entropy pool to ensure a large supply of entropy for 263 /dev/random and /dev/urandom and also provides direct access 264 via /dev/chaoskeyX 265 266 To compile this driver as a module, choose M here: the 267 module will be called chaoskey. 268