xref: /linux/drivers/usb/misc/Kconfig (revision a5766f11cfd3a0c03450d99c8fe548c2940be884)
1#
2# USB Miscellaneous driver configuration
3#
4comment "USB Miscellaneous drivers"
5	depends on USB
6
7config USB_EMI62
8	tristate "EMI 6|2m USB Audio interface support"
9	depends on USB
10	---help---
11	  This driver loads firmware to Emagic EMI 6|2m low latency USB
12	  Audio and Midi interface.
13
14	  After firmware load the device is handled with standard linux
15	  USB Audio driver.
16
17	  This code is also available as a module ( = code which can be
18	  inserted in and removed from the running kernel whenever you want).
19	  The module will be called audio. If you want to compile it as a
20	  module, say M here and read <file:Documentation/kbuild/modules.txt>.
21
22config USB_EMI26
23	tristate "EMI 2|6 USB Audio interface support"
24	depends on USB
25	---help---
26	  This driver loads firmware to Emagic EMI 2|6 low latency USB
27	  Audio interface.
28
29	  After firmware load the device is handled with standard linux
30	  USB Audio driver.
31
32	  To compile this driver as a module, choose M here: the
33	  module will be called emi26.
34
35config USB_ADUTUX
36	tristate "ADU devices from Ontrak Control Systems"
37	depends on USB
38	help
39	  Say Y if you want to use an ADU device from Ontrak Control
40	  Systems.
41
42	  To compile this driver as a module, choose M here.  The module
43	  will be called adutux.
44
45config USB_RIO500
46	tristate "USB Diamond Rio500 support"
47	depends on USB
48	help
49	  Say Y here if you want to connect a USB Rio500 mp3 player to your
50	  computer's USB port. Please read <file:Documentation/usb/rio.txt>
51	  for more information.
52
53	  To compile this driver as a module, choose M here: the
54	  module will be called rio500.
55
56config USB_LEGOTOWER
57	tristate "USB Lego Infrared Tower support"
58	depends on USB
59	help
60	  Say Y here if you want to connect a USB Lego Infrared Tower to your
61	  computer's USB port.
62
63	  This code is also available as a module ( = code which can be
64	  inserted in and removed from the running kernel whenever you want).
65	  The module will be called legousbtower. If you want to compile it as
66	  a module, say M here and read
67	  <file:Documentation/kbuild/modules.txt>.
68
69config USB_LCD
70	tristate "USB LCD driver support"
71	depends on USB
72	help
73	  Say Y here if you want to connect an USBLCD to your computer's
74	  USB port. The USBLCD is a small USB interface board for
75	  alphanumeric LCD modules. See <http://www.usblcd.de/> for more
76	  information.
77
78	  To compile this driver as a module, choose M here: the
79	  module will be called usblcd.
80
81config USB_BERRY_CHARGE
82	tristate "USB BlackBerry recharge support"
83	depends on USB
84	help
85	  Say Y here if you want to connect a BlackBerry device to your
86	  computer's USB port and have it automatically switch to "recharge"
87	  mode.
88
89	  To compile this driver as a module, choose M here: the
90	  module will be called berry_charge.
91
92config USB_LED
93	tristate "USB LED driver support"
94	depends on USB
95	help
96	  Say Y here if you want to connect an USBLED device to your
97	  computer's USB port.
98
99	  To compile this driver as a module, choose M here: the
100	  module will be called usbled.
101
102config USB_CYPRESS_CY7C63
103	tristate "Cypress CY7C63xxx USB driver support"
104	depends on USB
105	help
106	  Say Y here if you want to connect a Cypress CY7C63xxx
107	  micro controller to your computer's USB port. Currently this
108	  driver supports the pre-programmed devices (incl. firmware)
109	  by AK Modul-Bus Computer GmbH.
110
111	  Please see: http://www.ak-modul-bus.de/stat/mikrocontroller.html
112
113	  To compile this driver as a module, choose M here: the
114	  module will be called cypress_cy7c63.
115
116config USB_CYTHERM
117	tristate "Cypress USB thermometer driver support"
118	depends on USB
119	help
120	  Say Y here if you want to connect a Cypress USB thermometer
121	  device to your computer's USB port. This device is also known
122	  as the Cypress USB Starter kit or demo board. The Elektor
123	  magazine published a modified version of this device in issue
124	  #291.
125
126	  To compile this driver as a module, choose M here: the
127	  module will be called cytherm.
128
129config USB_PHIDGET
130	tristate "USB Phidgets drivers"
131	depends on USB
132	help
133	  Say Y here to enable the various drivers for devices from
134	  Phidgets inc.
135
136config USB_PHIDGETKIT
137	tristate "USB PhidgetInterfaceKit support"
138	depends on USB_PHIDGET
139	help
140	  Say Y here if you want to connect a PhidgetInterfaceKit USB device
141	  from Phidgets Inc.
142
143	  To compile this driver as a module, choose M here: the
144	  module will be called phidgetkit.
145
146config USB_PHIDGETMOTORCONTROL
147	tristate "USB PhidgetMotorControl support"
148	depends on USB_PHIDGET
149	help
150	  Say Y here if you want to connect a PhidgetMotorControl USB device
151	  from Phidgets Inc.
152
153	  To compile this driver as a module, choose M here: the
154	  module will be called phidgetmotorcontrol.
155
156config USB_PHIDGETSERVO
157	tristate "USB PhidgetServo support"
158	depends on USB_PHIDGET
159	help
160	  Say Y here if you want to connect an 1 or 4 Motor PhidgetServo
161	  servo controller version 2.0 or 3.0.
162
163	  Phidgets Inc. has a web page at <http://www.phidgets.com/>.
164
165	  To compile this driver as a module, choose M here: the
166	  module will be called phidgetservo.
167
168config USB_IDMOUSE
169	tristate "Siemens ID USB Mouse Fingerprint sensor support"
170	depends on USB
171	help
172	  Say Y here if you want to use the fingerprint sensor on
173	  the Siemens ID Mouse. There is also a Siemens ID Mouse
174	  _Professional_, which has not been tested with this driver,
175	  but uses the same sensor and may therefore work.
176
177	  This driver creates an entry "/dev/idmouseX" or "/dev/usb/idmouseX",
178	  which can be used by, e.g.,"cat /dev/idmouse0 > fingerprint.pnm".
179
180	  See also <http://www.fs.tum.de/~echtler/idmouse/>.
181
182config USB_FTDI_ELAN
183	tristate "Elan PCMCIA CardBus Adapter USB Client"
184	depends on USB
185	default M
186	help
187	  ELAN's Uxxx series of adapters are USB to PCMCIA CardBus adapters.
188	  Currently only the U132 adapter is available.
189
190	  The U132 is specifically designed for CardBus PC cards that contain
191	  an OHCI host controller. Typical PC cards are the Orange Mobile 3G
192	  Option GlobeTrotter Fusion card. The U132 adapter will *NOT* work
193	  with PC cards that do not contain an OHCI controller. To use a U132
194	  adapter you will need this "ftdi-elan" module as well as the "u132-hcd"
195	  module which is a USB host controller driver that talks to the OHCI
196	  controller within CardBus card that are inserted in the U132 adapter.
197
198	  This driver has been tested with a CardBus OHCI USB adapter, and
199	  worked with a USB PEN Drive inserted into the first USB port of
200	  the PCCARD. A rather pointless thing to do, but useful for testing.
201
202	  See also the USB_U132_HCD entry "Elan U132 Adapter Host Controller"
203
204	  It is safe to say M here.
205
206config USB_APPLEDISPLAY
207	tristate "Apple Cinema Display support"
208	depends on USB
209	select BACKLIGHT_LCD_SUPPORT
210	select BACKLIGHT_CLASS_DEVICE
211	help
212	  Say Y here if you want to control the backlight of Apple Cinema
213	  Displays over USB. This driver provides a sysfs interface.
214
215source "drivers/usb/misc/sisusbvga/Kconfig"
216
217config USB_LD
218	tristate "USB LD driver"
219	depends on USB
220	help
221	  This driver is for generic USB devices that use interrupt transfers,
222	  like LD Didactic's USB devices.
223
224	  To compile this driver as a module, choose M here: the
225	  module will be called ldusb.
226
227config USB_TRANCEVIBRATOR
228	tristate "PlayStation 2 Trance Vibrator driver support"
229	depends on USB
230	help
231	  Say Y here if you want to connect a PlayStation 2 Trance Vibrator
232	  device to your computer's USB port.
233
234	  To compile this driver as a module, choose M here: the
235	  module will be called trancevibrator.
236
237config USB_IOWARRIOR
238	tristate "IO Warrior driver support"
239	depends on USB
240	help
241	  Say Y here if you want to support the IO Warrior devices from Code
242	  Mercenaries.  This includes support for the following devices:
243	  	IO Warrior 40
244		IO Warrior 24
245		IO Warrior 56
246		IO Warrior 24 Power Vampire
247
248	  To compile this driver as a module, choose M here: the
249	  module will be called iowarrior.
250
251config USB_TEST
252	tristate "USB testing driver"
253	depends on USB && USB_DEVICEFS
254	help
255	  This driver is for testing host controller software.  It is used
256	  with specialized device firmware for regression and stress testing,
257	  to help prevent problems from cropping up with "real" drivers.
258
259	  See <http://www.linux-usb.org/usbtest/> for more information,
260	  including sample test device firmware and "how to use it".
261
262config USB_ISIGHTFW
263	tristate "iSight firmware loading support"
264	depends on USB
265	select FW_LOADER
266	help
267	  This driver loads firmware for USB Apple iSight cameras, allowing
268	  them to be driven by the USB video class driver available at
269	  http://linux-uvc.berlios.de
270
271	  The firmware for this driver must be extracted from the MacOS
272	  driver beforehand. Tools for doing so are available at
273	  http://bersace03.free.fr
274