diff options
Diffstat (limited to 'drivers/usb/misc/Kconfig')
-rw-r--r-- | drivers/usb/misc/Kconfig | 152 |
1 files changed, 152 insertions, 0 deletions
diff --git a/drivers/usb/misc/Kconfig b/drivers/usb/misc/Kconfig new file mode 100644 index 000000000000..3a896954b3a9 --- /dev/null +++ b/drivers/usb/misc/Kconfig | |||
@@ -0,0 +1,152 @@ | |||
1 | # | ||
2 | # USB Miscellaneous driver configuration | ||
3 | # | ||
4 | comment "USB Miscellaneous drivers" | ||
5 | depends on USB | ||
6 | |||
7 | config 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 | |||
22 | config 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 | |||
35 | config USB_AUERSWALD | ||
36 | tristate "USB Auerswald ISDN support (EXPERIMENTAL)" | ||
37 | depends on USB && EXPERIMENTAL | ||
38 | help | ||
39 | Say Y here if you want to connect an Auerswald USB ISDN Device | ||
40 | to your computer's USB port. | ||
41 | |||
42 | To compile this driver as a module, choose M here: the | ||
43 | module will be called auerswald. | ||
44 | |||
45 | config USB_RIO500 | ||
46 | tristate "USB Diamond Rio500 support (EXPERIMENTAL)" | ||
47 | depends on USB && EXPERIMENTAL | ||
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 | |||
56 | config USB_LEGOTOWER | ||
57 | tristate "USB Lego Infrared Tower support (EXPERIMENTAL)" | ||
58 | depends on USB && EXPERIMENTAL | ||
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 | |||
69 | config 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 | |||
81 | config USB_LED | ||
82 | tristate "USB LED driver support" | ||
83 | depends on USB | ||
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 | |||
91 | config USB_CYTHERM | ||
92 | tristate "Cypress USB thermometer driver support" | ||
93 | depends on USB | ||
94 | help | ||
95 | Say Y here if you want to connect a Cypress USB thermometer | ||
96 | device to your computer's USB port. This device is also known | ||
97 | as the Cypress USB Starter kit or demo board. The Elektor | ||
98 | magazine published a modified version of this device in issue | ||
99 | #291. | ||
100 | |||
101 | To compile this driver as a module, choose M here: the | ||
102 | module will be called cytherm. | ||
103 | |||
104 | config USB_PHIDGETKIT | ||
105 | tristate "USB PhidgetKit support" | ||
106 | depends on USB | ||
107 | help | ||
108 | Say Y here if you want to connect a PhidgetKit USB device from | ||
109 | Phidgets Inc. | ||
110 | |||
111 | To compile this driver as a module, choose M here: the | ||
112 | module will be called phidgetkit. | ||
113 | |||
114 | config USB_PHIDGETSERVO | ||
115 | tristate "USB PhidgetServo support" | ||
116 | depends on USB | ||
117 | help | ||
118 | Say Y here if you want to connect an 1 or 4 Motor PhidgetServo | ||
119 | servo controller version 2.0 or 3.0. | ||
120 | |||
121 | Phidgets Inc. has a web page at <http://www.phidgets.com/>. | ||
122 | |||
123 | To compile this driver as a module, choose M here: the | ||
124 | module will be called phidgetservo. | ||
125 | |||
126 | config USB_IDMOUSE | ||
127 | tristate "Siemens ID USB Mouse Fingerprint sensor support" | ||
128 | depends on USB | ||
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 <http://www.fs.tum.de/~echtler/idmouse/>. | ||
139 | |||
140 | source "drivers/usb/misc/sisusbvga/Kconfig" | ||
141 | |||
142 | config USB_TEST | ||
143 | tristate "USB testing driver (DEVELOPMENT)" | ||
144 | depends on USB && USB_DEVICEFS && EXPERIMENTAL | ||
145 | help | ||
146 | This driver is for testing host controller software. It is used | ||
147 | with specialized device firmware for regression and stress testing, | ||
148 | to help prevent problems from cropping up with "real" drivers. | ||
149 | |||
150 | See <http://www.linux-usb.org/usbtest/> for more information, | ||
151 | including sample test device firmware and "how to use it". | ||
152 | |||