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_LED
83	tristate "USB LED driver support"
84	help
85	  Say Y here if you want to connect an USBLED device to your 
86	  computer's USB port.
87
88	  To compile this driver as a module, choose M here: the
89	  module will be called usbled.
90
91config USB_CYPRESS_CY7C63
92	tristate "Cypress CY7C63xxx USB driver support"
93	help
94	  Say Y here if you want to connect a Cypress CY7C63xxx
95	  micro controller to your computer's USB port. Currently this
96	  driver supports the pre-programmed devices (incl. firmware)
97	  by AK Modul-Bus Computer GmbH.
98
99	  Please see: http://www.ak-modul-bus.de/stat/mikrocontroller.html
100
101	  To compile this driver as a module, choose M here: the
102	  module will be called cypress_cy7c63.
103
104config USB_CYTHERM
105	tristate "Cypress USB thermometer driver support"
106	help
107	  Say Y here if you want to connect a Cypress USB thermometer
108	  device to your computer's USB port. This device is also known
109	  as the Cypress USB Starter kit or demo board. The Elektor
110	  magazine published a modified version of this device in issue 
111	  #291.
112
113	  To compile this driver as a module, choose M here: the
114	  module will be called cytherm.
115
116config USB_IDMOUSE
117	tristate "Siemens ID USB Mouse Fingerprint sensor support"
118	help
119	  Say Y here if you want to use the fingerprint sensor on
120	  the Siemens ID Mouse. There is also a Siemens ID Mouse
121	  _Professional_, which has not been tested with this driver,
122	  but uses the same sensor and may therefore work.
123
124	  This driver creates an entry "/dev/idmouseX" or "/dev/usb/idmouseX",
125	  which can be used by, e.g.,"cat /dev/idmouse0 > fingerprint.pnm".
126
127	  See also <http://www.fs.tum.de/~echtler/idmouse/>.
128
129config USB_FTDI_ELAN
130	tristate "Elan PCMCIA CardBus Adapter USB Client"
131	help
132	  ELAN's Uxxx series of adapters are USB to PCMCIA CardBus adapters.
133	  Currently only the U132 adapter is available.
134
135	  The U132 is specifically designed for CardBus PC cards that contain
136	  an OHCI host controller. Typical PC cards are the Orange Mobile 3G
137	  Option GlobeTrotter Fusion card. The U132 adapter will *NOT* work
138	  with PC cards that do not contain an OHCI controller. To use a U132
139	  adapter you will need this "ftdi-elan" module as well as the "u132-hcd"
140	  module which is a USB host controller driver that talks to the OHCI
141	  controller within CardBus card that are inserted in the U132 adapter.
142
143	  This driver has been tested with a CardBus OHCI USB adapter, and
144	  worked with a USB PEN Drive inserted into the first USB port of
145	  the PCCARD. A rather pointless thing to do, but useful for testing.
146
147	  See also the USB_U132_HCD entry "Elan U132 Adapter Host Controller"
148
149	  It is safe to say M here.
150
151config USB_APPLEDISPLAY
152	tristate "Apple Cinema Display support"
153	select BACKLIGHT_LCD_SUPPORT
154	select BACKLIGHT_CLASS_DEVICE
155	help
156	  Say Y here if you want to control the backlight of Apple Cinema
157	  Displays over USB. This driver provides a sysfs interface.
158
159source "drivers/usb/misc/sisusbvga/Kconfig"
160
161config USB_LD
162	tristate "USB LD driver"
163	help
164	  This driver is for generic USB devices that use interrupt transfers,
165	  like LD Didactic's USB devices.
166
167	  To compile this driver as a module, choose M here: the
168	  module will be called ldusb.
169
170config USB_TRANCEVIBRATOR
171	tristate "PlayStation 2 Trance Vibrator driver support"
172	help
173	  Say Y here if you want to connect a PlayStation 2 Trance Vibrator
174	  device to your computer's USB port.
175
176	  To compile this driver as a module, choose M here: the
177	  module will be called trancevibrator.
178
179config USB_IOWARRIOR
180	tristate "IO Warrior driver support"
181	help
182	  Say Y here if you want to support the IO Warrior devices from Code
183	  Mercenaries.  This includes support for the following devices:
184	  	IO Warrior 40
185		IO Warrior 24
186		IO Warrior 56
187		IO Warrior 24 Power Vampire
188
189	  To compile this driver as a module, choose M here: the
190	  module will be called iowarrior.
191
192config USB_TEST
193	tristate "USB testing driver"
194	help
195	  This driver is for testing host controller software.  It is used
196	  with specialized device firmware for regression and stress testing,
197	  to help prevent problems from cropping up with "real" drivers.
198
199	  See <http://www.linux-usb.org/usbtest/> for more information,
200	  including sample test device firmware and "how to use it".
201
202config USB_EHSET_TEST_FIXTURE
203        tristate "USB EHSET Test Fixture driver"
204        help
205	  Say Y here if you want to support the special test fixture device
206	  used for the USB-IF Embedded Host High-Speed Electrical Test procedure.
207
208	  When the test fixture is connected, it can enumerate as one of several
209	  VID/PID pairs. This driver then initiates a corresponding test mode on
210	  the downstream port to which the test fixture is attached.
211
212	  See <http://www.usb.org/developers/onthego/EHSET_v1.01.pdf> for more
213	  information.
214
215config USB_ISIGHTFW
216	tristate "iSight firmware loading support"
217	select FW_LOADER
218	help
219	  This driver loads firmware for USB Apple iSight cameras, allowing
220	  them to be driven by the USB video class driver available at
221	  http://linux-uvc.berlios.de
222
223	  The firmware for this driver must be extracted from the MacOS
224	  driver beforehand. Tools for doing so are available at
225	  http://bersace03.free.fr
226
227config USB_YUREX
228	tristate "USB YUREX driver support"
229	help
230	  Say Y here if you want to connect a YUREX to your computer's
231	  USB port. The YUREX is a leg-shakes sensor. See
232	  <http://bbu.kayac.com/en/> for further information.
233	  This driver supports read/write of leg-shakes counter and
234	  fasync for the counter update via a device file /dev/yurex*.
235
236	  To compile this driver as a module, choose M here: the
237	  module will be called yurex.
238
239config USB_EZUSB_FX2
240	tristate "Functions for loading firmware on EZUSB chips"
241	help
242	  Say Y here if you need EZUSB device support.
243	  (Cypress FX/FX2/FX2LP microcontrollers)
244
245config USB_HSIC_USB3503
246       tristate "USB3503 HSIC to USB20 Driver"
247       depends on I2C
248       select REGMAP_I2C
249       help
250         This option enables support for SMSC USB3503 HSIC to USB 2.0 Driver.
251
252config USB_LINK_LAYER_TEST
253	tristate "USB Link Layer Test driver"
254	help
255	  This driver is for generating specific traffic for Super Speed Link
256	  Layer Test Device. Say Y only when you want to conduct USB Super Speed
257	  Link Layer Test for host controllers.
258
259config USB_CHAOSKEY
260	tristate "ChaosKey random number generator driver support"
261	depends on HW_RANDOM
262	help
263	  Say Y here if you want to connect an AltusMetrum ChaosKey to
264	  your computer's USB port. The ChaosKey is a hardware random
265	  number generator which hooks into the kernel entropy pool to
266	  ensure a large supply of entropy for /dev/random and
267	  /dev/urandom and also provides direct access via /dev/chaoskeyX
268
269	  To compile this driver as a module, choose M here: the
270	  module will be called chaoskey.
271