Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # USB Input driver configuration | |
3 | # | |
4 | comment "USB Input Devices" | |
5 | depends on USB | |
6 | ||
7 | config USB_HID | |
8 | tristate "USB Human Interface Device (full HID) support" | |
9 | depends on USB | |
10 | ---help--- | |
11 | Say Y here if you want full HID support to connect keyboards, | |
12 | mice, joysticks, graphic tablets, or any other HID based devices | |
13 | to your computer via USB. You also need to select HID Input layer | |
14 | support (below) if you want to use keyboards, mice, joysticks and | |
15 | the like ... as well as Uninterruptible Power Supply (UPS) and | |
16 | monitor control devices. | |
17 | ||
18 | You can't use this driver and the HIDBP (Boot Protocol) keyboard | |
19 | and mouse drivers at the same time. More information is available: | |
20 | <file:Documentation/input/input.txt>. | |
21 | ||
22 | If unsure, say Y. | |
23 | ||
24 | To compile this driver as a module, choose M here: the | |
25 | module will be called usbhid. | |
26 | ||
27 | comment "Input core support is needed for USB HID input layer or HIDBP support" | |
28 | depends on USB_HID && INPUT=n | |
29 | ||
30 | config USB_HIDINPUT | |
31 | bool "HID input layer support" | |
32 | default y | |
33 | depends on INPUT && USB_HID | |
34 | help | |
35 | Say Y here if you want to use a USB keyboard, mouse or joystick, | |
36 | or any other HID input device. | |
37 | ||
38 | If unsure, say Y. | |
39 | ||
eab9edd2 MH |
40 | config USB_HIDINPUT_POWERBOOK |
41 | bool "Enable support for iBook/PowerBook special keys" | |
42 | default n | |
43 | depends on USB_HIDINPUT | |
44 | help | |
45 | Say Y here if you want support for the special keys (Fn, Numlock) on | |
46 | Apple iBooks and PowerBooks. | |
47 | ||
48 | If unsure, say N. | |
49 | ||
1da177e4 LT |
50 | config HID_FF |
51 | bool "Force feedback support (EXPERIMENTAL)" | |
52 | depends on USB_HIDINPUT && EXPERIMENTAL | |
53 | help | |
54 | Say Y here is you want force feedback support for a few HID devices. | |
55 | See below for a list of supported devices. | |
56 | ||
57 | See <file:Documentation/input/ff.txt> for a description of the force | |
58 | feedback API. | |
59 | ||
60 | If unsure, say N. | |
61 | ||
62 | config HID_PID | |
224ee88f | 63 | bool "PID device support" |
1da177e4 LT |
64 | depends on HID_FF |
65 | help | |
224ee88f AH |
66 | Say Y here if you have a PID-compliant device and wish to enable force |
67 | feedback for it. Microsoft Sidewinder Force Feedback 2 is one of such | |
68 | devices. | |
1da177e4 LT |
69 | |
70 | config LOGITECH_FF | |
71 | bool "Logitech WingMan *3D support" | |
72 | depends on HID_FF | |
dc76c912 | 73 | select INPUT_FF_MEMLESS if USB_HID |
1da177e4 LT |
74 | help |
75 | Say Y here if you have one of these devices: | |
76 | - Logitech WingMan Cordless RumblePad | |
77 | - Logitech WingMan Force 3D | |
78 | and if you want to enable force feedback for them. | |
79 | Note: if you say N here, this device will still be supported, but without | |
80 | force feedback. | |
81 | ||
82 | config THRUSTMASTER_FF | |
83 | bool "ThrustMaster FireStorm Dual Power 2 support (EXPERIMENTAL)" | |
84 | depends on HID_FF && EXPERIMENTAL | |
dc76c912 | 85 | select INPUT_FF_MEMLESS if USB_HID |
1da177e4 LT |
86 | help |
87 | Say Y here if you have a THRUSTMASTER FireStore Dual Power 2, | |
88 | and want to enable force feedback support for it. | |
89 | Note: if you say N here, this device will still be supported, but without | |
90 | force feedback. | |
91 | ||
bb3caf7f AH |
92 | config ZEROPLUS_FF |
93 | bool "Zeroplus based game controller support" | |
94 | depends on HID_FF | |
95 | select INPUT_FF_MEMLESS if USB_HID | |
96 | help | |
97 | Say Y here if you have a Zeroplus based game controller and want to | |
98 | enable force feedback for it. | |
99 | ||
1da177e4 LT |
100 | config USB_HIDDEV |
101 | bool "/dev/hiddev raw HID device support" | |
102 | depends on USB_HID | |
103 | help | |
104 | Say Y here if you want to support HID devices (from the USB | |
105 | specification standpoint) that aren't strictly user interface | |
106 | devices, like monitor controls and Uninterruptable Power Supplies. | |
107 | ||
108 | This module supports these devices separately using a separate | |
109 | event interface on /dev/usb/hiddevX (char 180:96 to 180:111). | |
110 | ||
111 | If unsure, say Y. | |
112 | ||
113 | menu "USB HID Boot Protocol drivers" | |
114 | depends on USB!=n && USB_HID!=y | |
115 | ||
116 | config USB_KBD | |
117 | tristate "USB HIDBP Keyboard (simple Boot) support" | |
118 | depends on USB && INPUT | |
119 | ---help--- | |
120 | Say Y here only if you are absolutely sure that you don't want | |
121 | to use the generic HID driver for your USB keyboard and prefer | |
122 | to use the keyboard in its limited Boot Protocol mode instead. | |
123 | ||
124 | This is almost certainly not what you want. This is mostly | |
125 | useful for embedded applications or simple keyboards. | |
126 | ||
127 | To compile this driver as a module, choose M here: the | |
128 | module will be called usbkbd. | |
129 | ||
130 | If even remotely unsure, say N. | |
131 | ||
132 | config USB_MOUSE | |
133 | tristate "USB HIDBP Mouse (simple Boot) support" | |
134 | depends on USB && INPUT | |
135 | ---help--- | |
136 | Say Y here only if you are absolutely sure that you don't want | |
137 | to use the generic HID driver for your USB mouse and prefer | |
138 | to use the mouse in its limited Boot Protocol mode instead. | |
139 | ||
140 | This is almost certainly not what you want. This is mostly | |
141 | useful for embedded applications or simple mice. | |
142 | ||
143 | To compile this driver as a module, choose M here: the | |
144 | module will be called usbmouse. | |
145 | ||
146 | If even remotely unsure, say N. | |
147 | ||
148 | endmenu | |
149 | ||
150 | config USB_AIPTEK | |
151 | tristate "Aiptek 6000U/8000U tablet support" | |
152 | depends on USB && INPUT | |
153 | help | |
154 | Say Y here if you want to use the USB version of the Aiptek 6000U | |
155 | or Aiptek 8000U tablet. Make sure to say Y to "Mouse support" | |
156 | (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" | |
157 | (CONFIG_INPUT_EVDEV) as well. | |
158 | ||
159 | To compile this driver as a module, choose M here: the | |
160 | module will be called aiptek. | |
161 | ||
162 | config USB_WACOM | |
163 | tristate "Wacom Intuos/Graphire tablet support" | |
164 | depends on USB && INPUT | |
165 | help | |
166 | Say Y here if you want to use the USB version of the Wacom Intuos | |
167 | or Graphire tablet. Make sure to say Y to "Mouse support" | |
168 | (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" | |
169 | (CONFIG_INPUT_EVDEV) as well. | |
170 | ||
171 | To compile this driver as a module, choose M here: the | |
172 | module will be called wacom. | |
173 | ||
53880546 SV |
174 | config USB_ACECAD |
175 | tristate "Acecad Flair tablet support" | |
176 | depends on USB && INPUT | |
177 | help | |
178 | Say Y here if you want to use the USB version of the Acecad Flair | |
179 | tablet. Make sure to say Y to "Mouse support" | |
180 | (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" | |
181 | (CONFIG_INPUT_EVDEV) as well. | |
182 | ||
183 | To compile this driver as a module, choose M here: the | |
184 | module will be called acecad. | |
185 | ||
1da177e4 LT |
186 | config USB_KBTAB |
187 | tristate "KB Gear JamStudio tablet support" | |
188 | depends on USB && INPUT | |
189 | help | |
190 | Say Y here if you want to use the USB version of the KB Gear | |
191 | JamStudio tablet. Make sure to say Y to "Mouse support" | |
192 | (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" | |
193 | (CONFIG_INPUT_EVDEV) as well. | |
194 | ||
195 | To compile this driver as a module, choose M here: the | |
196 | module will be called kbtab. | |
197 | ||
198 | config USB_POWERMATE | |
199 | tristate "Griffin PowerMate and Contour Jog support" | |
200 | depends on USB && INPUT | |
201 | ---help--- | |
202 | Say Y here if you want to use Griffin PowerMate or Contour Jog devices. | |
203 | These are aluminum dials which can measure clockwise and anticlockwise | |
204 | rotation. The dial also acts as a pushbutton. The base contains an LED | |
205 | which can be instructed to pulse or to switch to a particular intensity. | |
206 | ||
207 | You can download userspace tools from | |
208 | <http://sowerbutts.com/powermate/>. | |
209 | ||
210 | To compile this driver as a module, choose M here: the | |
211 | module will be called powermate. | |
212 | ||
1d3e2023 DR |
213 | config USB_TOUCHSCREEN |
214 | tristate "USB Touchscreen Driver" | |
215 | depends on USB && INPUT | |
216 | ---help--- | |
217 | USB Touchscreen driver for: | |
218 | - eGalax Touchkit USB | |
219 | - PanJit TouchSet USB | |
220 | - 3M MicroTouch USB | |
221 | - ITM | |
222 | ||
223 | Have a look at <http://linux.chapter7.ch/touchkit/> for | |
224 | a usage description and the required user-space stuff. | |
225 | ||
226 | To compile this driver as a module, choose M here: the | |
227 | module will be called usbtouchscreen. | |
228 | ||
229 | config USB_TOUCHSCREEN_EGALAX | |
230 | default y | |
231 | bool "eGalax device support" if EMBEDDED | |
232 | depends on USB_TOUCHSCREEN | |
233 | ||
234 | config USB_TOUCHSCREEN_PANJIT | |
235 | default y | |
236 | bool "PanJit device support" if EMBEDDED | |
237 | depends on USB_TOUCHSCREEN | |
238 | ||
239 | config USB_TOUCHSCREEN_3M | |
240 | default y | |
241 | bool "3M/Microtouch device support" if EMBEDDED | |
242 | depends on USB_TOUCHSCREEN | |
243 | ||
244 | config USB_TOUCHSCREEN_ITM | |
245 | default y | |
246 | bool "ITM device support" if EMBEDDED | |
247 | depends on USB_TOUCHSCREEN | |
248 | ||
aca951a2 H |
249 | config USB_YEALINK |
250 | tristate "Yealink usb-p1k voip phone" | |
251 | depends on USB && INPUT && EXPERIMENTAL | |
252 | ---help--- | |
253 | Say Y here if you want to enable keyboard and LCD functions of the | |
254 | Yealink usb-p1k usb phones. The audio part is enabled by the generic | |
255 | usb sound driver, so you might want to enable that as well. | |
256 | ||
257 | For information about how to use these additional functions, see | |
258 | <file:Documentation/input/yealink.txt>. | |
259 | ||
260 | To compile this driver as a module, choose M here: the module will be | |
261 | called yealink. | |
262 | ||
1da177e4 LT |
263 | config USB_XPAD |
264 | tristate "X-Box gamepad support" | |
265 | depends on USB && INPUT | |
266 | ---help--- | |
267 | Say Y here if you want to use the X-Box pad with your computer. | |
268 | Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV) | |
269 | and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well. | |
270 | ||
271 | For information about how to connect the X-Box pad to USB, see | |
272 | <file:Documentation/input/xpad.txt>. | |
273 | ||
274 | To compile this driver as a module, choose M here: the | |
275 | module will be called xpad. | |
276 | ||
277 | config USB_ATI_REMOTE | |
278 | tristate "ATI / X10 USB RF remote control" | |
279 | depends on USB && INPUT | |
280 | ---help--- | |
281 | Say Y here if you want to use an ATI or X10 "Lola" USB remote control. | |
282 | These are RF remotes with USB receivers. | |
283 | The ATI remote comes with many of ATI's All-In-Wonder video cards. | |
284 | The X10 "Lola" remote is available at: | |
285 | <http://www.x10.com/products/lola_sg1.htm> | |
286 | This driver provides mouse pointer, left and right mouse buttons, | |
287 | and maps all the other remote buttons to keypress events. | |
288 | ||
289 | To compile this driver as a module, choose M here: the module will be | |
290 | called ati_remote. | |
291 |