2 # USB Miscellaneous driver configuration
4 comment "USB Miscellaneous drivers"
7 tristate "EMI 6|2m USB Audio interface support"
9 This driver loads firmware to Emagic EMI 6|2m low latency USB
10 Audio and Midi interface.
12 After firmware load the device is handled with standard linux
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>.
21 tristate "EMI 2|6 USB Audio interface support"
23 This driver loads firmware to Emagic EMI 2|6 low latency USB
26 After firmware load the device is handled with standard linux
29 To compile this driver as a module, choose M here: the
30 module will be called emi26.
33 tristate "ADU devices from Ontrak Control Systems"
35 Say Y if you want to use an ADU device from Ontrak Control
38 To compile this driver as a module, choose M here. The module
39 will be called adutux.
42 tristate "USB 7-Segment LED Display"
44 Say Y here if you have a USB 7-Segment Display by Delcom
46 To compile this driver as a module, choose M here: the
47 module will be called usbsevseg.
50 tristate "USB Lego Infrared Tower support"
52 Say Y here if you want to connect a USB Lego Infrared Tower to your
55 This code is also available as a module ( = code which can be
56 inserted in and removed from the running kernel whenever you want).
57 The module will be called legousbtower. If you want to compile it as
58 a module, say M here and read
59 <file:Documentation/kbuild/modules.txt>.
62 tristate "USB LCD driver support"
64 Say Y here if you want to connect an USBLCD to your computer's
65 USB port. The USBLCD is a small USB interface board for
66 alphanumeric LCD modules. See <http://www.usblcd.de/> for more
69 To compile this driver as a module, choose M here: the
70 module will be called usblcd.
72 config USB_CYPRESS_CY7C63
73 tristate "Cypress CY7C63xxx USB driver support"
75 Say Y here if you want to connect a Cypress CY7C63xxx
76 micro controller to your computer's USB port. Currently this
77 driver supports the pre-programmed devices (incl. firmware)
78 by AK Modul-Bus Computer GmbH.
80 Please see: http://www.ak-modul-bus.de/stat/mikrocontroller.html
82 To compile this driver as a module, choose M here: the
83 module will be called cypress_cy7c63.
86 tristate "Cypress USB thermometer driver support"
88 Say Y here if you want to connect a Cypress USB thermometer
89 device to your computer's USB port. This device is also known
90 as the Cypress USB Starter kit or demo board. The Elektor
91 magazine published a modified version of this device in issue
94 To compile this driver as a module, choose M here: the
95 module will be called cytherm.
98 tristate "Siemens ID USB Mouse Fingerprint sensor support"
100 Say Y here if you want to use the fingerprint sensor on
101 the Siemens ID Mouse. There is also a Siemens ID Mouse
102 _Professional_, which has not been tested with this driver,
103 but uses the same sensor and may therefore work.
105 This driver creates an entry "/dev/idmouseX" or "/dev/usb/idmouseX",
106 which can be used by, e.g.,"cat /dev/idmouse0 > fingerprint.pnm".
108 See also <http://www.fs.tum.de/~echtler/idmouse/>.
111 tristate "Elan PCMCIA CardBus Adapter USB Client"
113 ELAN's Uxxx series of adapters are USB to PCMCIA CardBus adapters.
114 Currently only the U132 adapter is available.
116 The U132 is specifically designed for CardBus PC cards that contain
117 an OHCI host controller. Typical PC cards are the Orange Mobile 3G
118 Option GlobeTrotter Fusion card. The U132 adapter will *NOT* work
119 with PC cards that do not contain an OHCI controller. To use a U132
120 adapter you will need this "ftdi-elan" module as well as the "u132-hcd"
121 module which is a USB host controller driver that talks to the OHCI
122 controller within CardBus card that are inserted in the U132 adapter.
124 This driver has been tested with a CardBus OHCI USB adapter, and
125 worked with a USB PEN Drive inserted into the first USB port of
126 the PCCARD. A rather pointless thing to do, but useful for testing.
128 See also the USB_U132_HCD entry "Elan U132 Adapter Host Controller"
130 It is safe to say M here.
132 config USB_APPLEDISPLAY
133 tristate "Apple Cinema Display support"
134 select BACKLIGHT_LCD_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.
140 source "drivers/usb/misc/sisusbvga/Kconfig"
143 tristate "USB LD driver"
145 This driver is for generic USB devices that use interrupt transfers,
146 like LD Didactic's USB devices.
148 To compile this driver as a module, choose M here: the
149 module will be called ldusb.
151 config USB_TRANCEVIBRATOR
152 tristate "PlayStation 2 Trance Vibrator driver support"
154 Say Y here if you want to connect a PlayStation 2 Trance Vibrator
155 device to your computer's USB port.
157 To compile this driver as a module, choose M here: the
158 module will be called trancevibrator.
161 tristate "IO Warrior driver support"
163 Say Y here if you want to support the IO Warrior devices from Code
164 Mercenaries. This includes support for the following devices:
168 IO Warrior 24 Power Vampire
170 To compile this driver as a module, choose M here: the
171 module will be called iowarrior.
174 tristate "USB testing driver"
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.
180 See <http://www.linux-usb.org/usbtest/> for more information,
181 including sample test device firmware and "how to use it".
183 config USB_EHSET_TEST_FIXTURE
184 tristate "USB EHSET Test Fixture driver"
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.
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.
193 See <http://www.usb.org/developers/onthego/EHSET_v1.01.pdf> for more
197 tristate "iSight firmware loading support"
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
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
209 tristate "USB YUREX driver support"
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*.
217 To compile this driver as a module, choose M here: the
218 module will be called yurex.
221 tristate "Functions for loading firmware on EZUSB chips"
223 Say Y here if you need EZUSB device support.
224 (Cypress FX/FX2/FX2LP microcontrollers)
226 config USB_HSIC_USB3503
227 tristate "USB3503 HSIC to USB20 Driver"
231 This option enables support for SMSC USB3503 HSIC to USB 2.0 Driver.
233 config USB_HSIC_USB4604
234 tristate "USB4604 HSIC to USB20 Driver"
237 This option enables support for SMSC USB4604 HSIC to USB 2.0 Driver.
239 config USB_LINK_LAYER_TEST
240 tristate "USB Link Layer Test driver"
242 This driver is for generating specific traffic for Super Speed Link
243 Layer Test Device. Say Y only when you want to conduct USB Super Speed
244 Link Layer Test for host controllers.
247 tristate "ChaosKey random number generator driver support"
250 Say Y here if you want to connect an AltusMetrum ChaosKey or
251 Araneus Alea I to your computer's USB port. These devices
252 are hardware random number generators which hook into the
253 kernel entropy pool to ensure a large supply of entropy for
254 /dev/random and /dev/urandom and also provides direct access
257 To compile this driver as a module, choose M here: the
258 module will be called chaoskey.
261 tristate "USB Type-C Connector System Software Interface driver"
264 UCSI driver is meant to be used as a convenience tool for desktop and
265 server systems that are not equipped to handle USB in device mode. It
266 will always select USB host role for the USB Type-C ports on systems
267 that provide UCSI interface.
269 USB Type-C Connector System Software Interface (UCSI) is a
270 specification for an interface that allows the Operating System to
271 control the USB Type-C ports on a system. Things the need controlling
272 include the USB Data Role (host or device), and when USB Power
273 Delivery is supported, the Power Role (source or sink). With USB
274 Type-C connectors, when two dual role capable devices are attached
275 together, the data role is selected randomly. Therefore it is
276 important to give the OS a way to select the role. Otherwise the user
277 would have to unplug and replug in order in order to attempt to swap
278 the data and power roles.
280 The UCSI specification can be downloaded from:
281 http://www.intel.com/content/www/us/en/io/universal-serial-bus/usb-type-c-ucsi-spec.html
283 To compile the driver as a module, choose M here: the module will be