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