Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
tjh.dev
kernel
os
linux
1#
2# USB Input driver configuration
3#
4comment "USB Input Devices"
5 depends on USB
6
7config USB_HID
8 tristate "USB Human Interface Device (full HID) support"
9 default y
10 depends on USB && INPUT
11 select HID
12 ---help---
13 Say Y here if you want full HID support to connect USB keyboards,
14 mice, joysticks, graphic tablets, or any other HID based devices
15 to your computer via USB, as well as Uninterruptible Power Supply
16 (UPS) and 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
27comment "Input core support is needed for USB HID input layer or HIDBP support"
28 depends on USB_HID && INPUT=n
29
30config USB_HIDINPUT_POWERBOOK
31 bool "Enable support for iBook/PowerBook special keys"
32 default n
33 depends on USB_HID
34 help
35 Say Y here if you want support for the special keys (Fn, Numlock) on
36 Apple iBooks and PowerBooks.
37
38 If unsure, say N.
39
40config HID_FF
41 bool "Force feedback support (EXPERIMENTAL)"
42 depends on USB_HID && EXPERIMENTAL
43 help
44 Say Y here is you want force feedback support for a few HID devices.
45 See below for a list of supported devices.
46
47 See <file:Documentation/input/ff.txt> for a description of the force
48 feedback API.
49
50 If unsure, say N.
51
52config HID_PID
53 bool "PID device support"
54 depends on HID_FF
55 help
56 Say Y here if you have a PID-compliant device and wish to enable force
57 feedback for it. Microsoft Sidewinder Force Feedback 2 is one of such
58 devices.
59
60config LOGITECH_FF
61 bool "Logitech devices support"
62 depends on HID_FF
63 select INPUT_FF_MEMLESS if USB_HID
64 help
65 Say Y here if you have one of these devices:
66 - Logitech WingMan Cordless RumblePad
67 - Logitech WingMan Cordless RumblePad 2
68 - Logitech WingMan Force 3D
69 - Logitech Formula Force EX
70 - Logitech MOMO Force wheel
71
72 and if you want to enable force feedback for them.
73 Note: if you say N here, this device will still be supported, but without
74 force feedback.
75
76config PANTHERLORD_FF
77 bool "PantherLord USB/PS2 2in1 Adapter support"
78 depends on HID_FF
79 select INPUT_FF_MEMLESS if USB_HID
80 help
81 Say Y here if you have a PantherLord USB/PS2 2in1 Adapter and want
82 to enable force feedback support for it.
83
84config THRUSTMASTER_FF
85 bool "ThrustMaster FireStorm Dual Power 2 support (EXPERIMENTAL)"
86 depends on HID_FF && EXPERIMENTAL
87 select INPUT_FF_MEMLESS if USB_HID
88 help
89 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2,
90 and want to enable force feedback support for it.
91 Note: if you say N here, this device will still be supported, but without
92 force feedback.
93
94config ZEROPLUS_FF
95 bool "Zeroplus based game controller support"
96 depends on HID_FF
97 select INPUT_FF_MEMLESS if USB_HID
98 help
99 Say Y here if you have a Zeroplus based game controller and want to
100 enable force feedback for it.
101
102config USB_HIDDEV
103 bool "/dev/hiddev raw HID device support"
104 depends on USB_HID
105 help
106 Say Y here if you want to support HID devices (from the USB
107 specification standpoint) that aren't strictly user interface
108 devices, like monitor controls and Uninterruptable Power Supplies.
109
110 This module supports these devices separately using a separate
111 event interface on /dev/usb/hiddevX (char 180:96 to 180:111).
112
113 If unsure, say Y.
114
115menu "USB HID Boot Protocol drivers"
116 depends on USB!=n && USB_HID!=y
117
118config USB_KBD
119 tristate "USB HIDBP Keyboard (simple Boot) support"
120 depends on USB && INPUT
121 ---help---
122 Say Y here only if you are absolutely sure that you don't want
123 to use the generic HID driver for your USB keyboard and prefer
124 to use the keyboard in its limited Boot Protocol mode instead.
125
126 This is almost certainly not what you want. This is mostly
127 useful for embedded applications or simple keyboards.
128
129 To compile this driver as a module, choose M here: the
130 module will be called usbkbd.
131
132 If even remotely unsure, say N.
133
134config USB_MOUSE
135 tristate "USB HIDBP Mouse (simple Boot) support"
136 depends on USB && INPUT
137 ---help---
138 Say Y here only if you are absolutely sure that you don't want
139 to use the generic HID driver for your USB mouse and prefer
140 to use the mouse in its limited Boot Protocol mode instead.
141
142 This is almost certainly not what you want. This is mostly
143 useful for embedded applications or simple mice.
144
145 To compile this driver as a module, choose M here: the
146 module will be called usbmouse.
147
148 If even remotely unsure, say N.
149
150endmenu
151
152config USB_AIPTEK
153 tristate "Aiptek 6000U/8000U tablet support"
154 depends on USB && INPUT
155 help
156 Say Y here if you want to use the USB version of the Aiptek 6000U
157 or Aiptek 8000U tablet. Make sure to say Y to "Mouse support"
158 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
159 (CONFIG_INPUT_EVDEV) as well.
160
161 To compile this driver as a module, choose M here: the
162 module will be called aiptek.
163
164config USB_WACOM
165 tristate "Wacom Intuos/Graphire tablet support"
166 depends on USB && INPUT
167 help
168 Say Y here if you want to use the USB version of the Wacom Intuos
169 or Graphire tablet. Make sure to say Y to "Mouse support"
170 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
171 (CONFIG_INPUT_EVDEV) as well.
172
173 To compile this driver as a module, choose M here: the
174 module will be called wacom.
175
176config USB_ACECAD
177 tristate "Acecad Flair tablet support"
178 depends on USB && INPUT
179 help
180 Say Y here if you want to use the USB version of the Acecad Flair
181 tablet. Make sure to say Y to "Mouse support"
182 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
183 (CONFIG_INPUT_EVDEV) as well.
184
185 To compile this driver as a module, choose M here: the
186 module will be called acecad.
187
188config USB_KBTAB
189 tristate "KB Gear JamStudio tablet support"
190 depends on USB && INPUT
191 help
192 Say Y here if you want to use the USB version of the KB Gear
193 JamStudio tablet. Make sure to say Y to "Mouse support"
194 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
195 (CONFIG_INPUT_EVDEV) as well.
196
197 To compile this driver as a module, choose M here: the
198 module will be called kbtab.
199
200config USB_POWERMATE
201 tristate "Griffin PowerMate and Contour Jog support"
202 depends on USB && INPUT
203 ---help---
204 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
205 These are aluminum dials which can measure clockwise and anticlockwise
206 rotation. The dial also acts as a pushbutton. The base contains an LED
207 which can be instructed to pulse or to switch to a particular intensity.
208
209 You can download userspace tools from
210 <http://sowerbutts.com/powermate/>.
211
212 To compile this driver as a module, choose M here: the
213 module will be called powermate.
214
215config USB_TOUCHSCREEN
216 tristate "USB Touchscreen Driver"
217 depends on USB && INPUT
218 ---help---
219 USB Touchscreen driver for:
220 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
221 - PanJit TouchSet USB
222 - 3M MicroTouch USB (EX II series)
223 - ITM
224 - some other eTurboTouch
225 - Gunze AHL61
226 - DMC TSC-10/25
227
228 Have a look at <http://linux.chapter7.ch/touchkit/> for
229 a usage description and the required user-space stuff.
230
231 To compile this driver as a module, choose M here: the
232 module will be called usbtouchscreen.
233
234config USB_TOUCHSCREEN_EGALAX
235 default y
236 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EMBEDDED
237 depends on USB_TOUCHSCREEN
238
239config USB_TOUCHSCREEN_PANJIT
240 default y
241 bool "PanJit device support" if EMBEDDED
242 depends on USB_TOUCHSCREEN
243
244config USB_TOUCHSCREEN_3M
245 default y
246 bool "3M/Microtouch EX II series device support" if EMBEDDED
247 depends on USB_TOUCHSCREEN
248
249config USB_TOUCHSCREEN_ITM
250 default y
251 bool "ITM device support" if EMBEDDED
252 depends on USB_TOUCHSCREEN
253
254config USB_TOUCHSCREEN_ETURBO
255 default y
256 bool "eTurboTouch (non-eGalax compatible) device support" if EMBEDDED
257 depends on USB_TOUCHSCREEN
258
259config USB_TOUCHSCREEN_GUNZE
260 default y
261 bool "Gunze AHL61 device support" if EMBEDDED
262 depends on USB_TOUCHSCREEN
263
264config USB_TOUCHSCREEN_DMC_TSC10
265 default y
266 bool "DMC TSC-10/25 device support" if EMBEDDED
267 depends on USB_TOUCHSCREEN
268
269config USB_YEALINK
270 tristate "Yealink usb-p1k voip phone"
271 depends on USB && INPUT && EXPERIMENTAL
272 ---help---
273 Say Y here if you want to enable keyboard and LCD functions of the
274 Yealink usb-p1k usb phones. The audio part is enabled by the generic
275 usb sound driver, so you might want to enable that as well.
276
277 For information about how to use these additional functions, see
278 <file:Documentation/input/yealink.txt>.
279
280 To compile this driver as a module, choose M here: the module will be
281 called yealink.
282
283config USB_XPAD
284 tristate "X-Box gamepad support"
285 depends on USB && INPUT
286 ---help---
287 Say Y here if you want to use the X-Box pad with your computer.
288 Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV)
289 and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well.
290
291 For information about how to connect the X-Box pad to USB, see
292 <file:Documentation/input/xpad.txt>.
293
294 To compile this driver as a module, choose M here: the
295 module will be called xpad.
296
297config USB_ATI_REMOTE
298 tristate "ATI / X10 USB RF remote control"
299 depends on USB && INPUT
300 ---help---
301 Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
302 These are RF remotes with USB receivers.
303 The ATI remote comes with many of ATI's All-In-Wonder video cards.
304 The X10 "Lola" remote is available at:
305 <http://www.x10.com/products/lola_sg1.htm>
306 This driver provides mouse pointer, left and right mouse buttons,
307 and maps all the other remote buttons to keypress events.
308
309 To compile this driver as a module, choose M here: the module will be
310 called ati_remote.
311
312config USB_ATI_REMOTE2
313 tristate "ATI / Philips USB RF remote control"
314 depends on USB && INPUT
315 ---help---
316 Say Y here if you want to use an ATI or Philips USB RF remote control.
317 These are RF remotes with USB receivers.
318 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
319 and is also available as a separate product.
320 This driver provides mouse pointer, left and right mouse buttons,
321 and maps all the other remote buttons to keypress events.
322
323 To compile this driver as a module, choose M here: the module will be
324 called ati_remote2.
325
326config USB_KEYSPAN_REMOTE
327 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
328 depends on USB && INPUT && EXPERIMENTAL
329 ---help---
330 Say Y here if you want to use a Keyspan DMR USB remote control.
331 Currently only the UIA-11 type of receiver has been tested. The tag
332 on the receiver that connects to the USB port should have a P/N that
333 will tell you what type of DMR you have. The UIA-10 type is not
334 supported at this time. This driver maps all buttons to keypress
335 events.
336
337 To compile this driver as a module, choose M here: the module will
338 be called keyspan_remote.
339
340config USB_APPLETOUCH
341 tristate "Apple USB Touchpad support"
342 depends on USB && INPUT
343 ---help---
344 Say Y here if you want to use an Apple USB Touchpad.
345
346 These are the touchpads that can be found on post-February 2005
347 Apple Powerbooks (prior models have a Synaptics touchpad connected
348 to the ADB bus).
349
350 This driver provides a basic mouse driver but can be interfaced
351 with the synaptics X11 driver to provide acceleration and
352 scrolling in X11.
353
354 For further information, see
355 <file:Documentation/input/appletouch.txt>.
356
357 To compile this driver as a module, choose M here: the
358 module will be called appletouch.
359
360config USB_GTCO
361 tristate "GTCO CalComp/InterWrite USB Support"
362 depends on USB && INPUT
363 ---help---
364 Say Y here if you want to use the USB version of the GTCO
365 CalComp/InterWrite Tablet. Make sure to say Y to "Mouse support"
366 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
367 (CONFIG_INPUT_EVDEV) as well.
368
369 To compile this driver as a module, choose M here: the
370 module will be called gtco.