2 # USB Input driver configuration
4 comment "USB Input Devices"
8 tristate "USB Human Interface Device (full HID) support"
10 depends on USB && INPUT
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.
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>.
24 To compile this driver as a module, choose M here: the
25 module will be called usbhid.
27 comment "Input core support is needed for USB HID input layer or HIDBP support"
28 depends on USB_HID && INPUT=n
30 config USB_HIDINPUT_POWERBOOK
31 bool "Enable support for iBook/PowerBook special keys"
35 Say Y here if you want support for the special keys (Fn, Numlock) on
36 Apple iBooks and PowerBooks.
41 bool "Force feedback support (EXPERIMENTAL)"
42 depends on USB_HID && EXPERIMENTAL
44 Say Y here is you want force feedback support for a few HID devices.
45 See below for a list of supported devices.
47 See <file:Documentation/input/ff.txt> for a description of the force
53 bool "PID device support"
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
61 bool "Logitech WingMan *3D support"
63 select INPUT_FF_MEMLESS if USB_HID
65 Say Y here if you have one of these devices:
66 - Logitech WingMan Cordless RumblePad
67 - Logitech WingMan Force 3D
68 and if you want to enable force feedback for them.
69 Note: if you say N here, this device will still be supported, but without
72 config THRUSTMASTER_FF
73 bool "ThrustMaster FireStorm Dual Power 2 support (EXPERIMENTAL)"
74 depends on HID_FF && EXPERIMENTAL
75 select INPUT_FF_MEMLESS if USB_HID
77 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2,
78 and want to enable force feedback support for it.
79 Note: if you say N here, this device will still be supported, but without
83 bool "Zeroplus based game controller support"
85 select INPUT_FF_MEMLESS if USB_HID
87 Say Y here if you have a Zeroplus based game controller and want to
88 enable force feedback for it.
91 bool "/dev/hiddev raw HID device support"
94 Say Y here if you want to support HID devices (from the USB
95 specification standpoint) that aren't strictly user interface
96 devices, like monitor controls and Uninterruptable Power Supplies.
98 This module supports these devices separately using a separate
99 event interface on /dev/usb/hiddevX (char 180:96 to 180:111).
103 menu "USB HID Boot Protocol drivers"
104 depends on USB!=n && USB_HID!=y
107 tristate "USB HIDBP Keyboard (simple Boot) support"
108 depends on USB && INPUT
110 Say Y here only if you are absolutely sure that you don't want
111 to use the generic HID driver for your USB keyboard and prefer
112 to use the keyboard in its limited Boot Protocol mode instead.
114 This is almost certainly not what you want. This is mostly
115 useful for embedded applications or simple keyboards.
117 To compile this driver as a module, choose M here: the
118 module will be called usbkbd.
120 If even remotely unsure, say N.
123 tristate "USB HIDBP Mouse (simple Boot) support"
124 depends on USB && INPUT
126 Say Y here only if you are absolutely sure that you don't want
127 to use the generic HID driver for your USB mouse and prefer
128 to use the mouse in its limited Boot Protocol mode instead.
130 This is almost certainly not what you want. This is mostly
131 useful for embedded applications or simple mice.
133 To compile this driver as a module, choose M here: the
134 module will be called usbmouse.
136 If even remotely unsure, say N.
141 tristate "Aiptek 6000U/8000U tablet support"
142 depends on USB && INPUT
144 Say Y here if you want to use the USB version of the Aiptek 6000U
145 or Aiptek 8000U tablet. Make sure to say Y to "Mouse support"
146 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
147 (CONFIG_INPUT_EVDEV) as well.
149 To compile this driver as a module, choose M here: the
150 module will be called aiptek.
153 tristate "Wacom Intuos/Graphire tablet support"
154 depends on USB && INPUT
156 Say Y here if you want to use the USB version of the Wacom Intuos
157 or Graphire tablet. Make sure to say Y to "Mouse support"
158 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
159 (CONFIG_INPUT_EVDEV) as well.
161 To compile this driver as a module, choose M here: the
162 module will be called wacom.
165 tristate "Acecad Flair tablet support"
166 depends on USB && INPUT
168 Say Y here if you want to use the USB version of the Acecad Flair
169 tablet. Make sure to say Y to "Mouse support"
170 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
171 (CONFIG_INPUT_EVDEV) as well.
173 To compile this driver as a module, choose M here: the
174 module will be called acecad.
177 tristate "KB Gear JamStudio tablet support"
178 depends on USB && INPUT
180 Say Y here if you want to use the USB version of the KB Gear
181 JamStudio tablet. Make sure to say Y to "Mouse support"
182 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
183 (CONFIG_INPUT_EVDEV) as well.
185 To compile this driver as a module, choose M here: the
186 module will be called kbtab.
189 tristate "Griffin PowerMate and Contour Jog support"
190 depends on USB && INPUT
192 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
193 These are aluminum dials which can measure clockwise and anticlockwise
194 rotation. The dial also acts as a pushbutton. The base contains an LED
195 which can be instructed to pulse or to switch to a particular intensity.
197 You can download userspace tools from
198 <http://sowerbutts.com/powermate/>.
200 To compile this driver as a module, choose M here: the
201 module will be called powermate.
203 config USB_TOUCHSCREEN
204 tristate "USB Touchscreen Driver"
205 depends on USB && INPUT
207 USB Touchscreen driver for:
208 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
209 - PanJit TouchSet USB
210 - 3M MicroTouch USB (EX II series)
212 - some other eTurboTouch
216 Have a look at <http://linux.chapter7.ch/touchkit/> for
217 a usage description and the required user-space stuff.
219 To compile this driver as a module, choose M here: the
220 module will be called usbtouchscreen.
222 config USB_TOUCHSCREEN_EGALAX
224 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EMBEDDED
225 depends on USB_TOUCHSCREEN
227 config USB_TOUCHSCREEN_PANJIT
229 bool "PanJit device support" if EMBEDDED
230 depends on USB_TOUCHSCREEN
232 config USB_TOUCHSCREEN_3M
234 bool "3M/Microtouch EX II series device support" if EMBEDDED
235 depends on USB_TOUCHSCREEN
237 config USB_TOUCHSCREEN_ITM
239 bool "ITM device support" if EMBEDDED
240 depends on USB_TOUCHSCREEN
242 config USB_TOUCHSCREEN_ETURBO
244 bool "eTurboTouch (non-eGalax compatible) device support" if EMBEDDED
245 depends on USB_TOUCHSCREEN
247 config USB_TOUCHSCREEN_GUNZE
249 bool "Gunze AHL61 device support" if EMBEDDED
250 depends on USB_TOUCHSCREEN
252 config USB_TOUCHSCREEN_DMC_TSC10
254 bool "DMC TSC-10/25 device support" if EMBEDDED
255 depends on USB_TOUCHSCREEN
258 tristate "Yealink usb-p1k voip phone"
259 depends on USB && INPUT && EXPERIMENTAL
261 Say Y here if you want to enable keyboard and LCD functions of the
262 Yealink usb-p1k usb phones. The audio part is enabled by the generic
263 usb sound driver, so you might want to enable that as well.
265 For information about how to use these additional functions, see
266 <file:Documentation/input/yealink.txt>.
268 To compile this driver as a module, choose M here: the module will be
272 tristate "X-Box gamepad support"
273 depends on USB && INPUT
275 Say Y here if you want to use the X-Box pad with your computer.
276 Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV)
277 and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well.
279 For information about how to connect the X-Box pad to USB, see
280 <file:Documentation/input/xpad.txt>.
282 To compile this driver as a module, choose M here: the
283 module will be called xpad.
285 config USB_ATI_REMOTE
286 tristate "ATI / X10 USB RF remote control"
287 depends on USB && INPUT
289 Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
290 These are RF remotes with USB receivers.
291 The ATI remote comes with many of ATI's All-In-Wonder video cards.
292 The X10 "Lola" remote is available at:
293 <http://www.x10.com/products/lola_sg1.htm>
294 This driver provides mouse pointer, left and right mouse buttons,
295 and maps all the other remote buttons to keypress events.
297 To compile this driver as a module, choose M here: the module will be
300 config USB_ATI_REMOTE2
301 tristate "ATI / Philips USB RF remote control"
302 depends on USB && INPUT
304 Say Y here if you want to use an ATI or Philips USB RF remote control.
305 These are RF remotes with USB receivers.
306 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
307 and is also available as a separate product.
308 This driver provides mouse pointer, left and right mouse buttons,
309 and maps all the other remote buttons to keypress events.
311 To compile this driver as a module, choose M here: the module will be
314 config USB_KEYSPAN_REMOTE
315 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
316 depends on USB && INPUT && EXPERIMENTAL
318 Say Y here if you want to use a Keyspan DMR USB remote control.
319 Currently only the UIA-11 type of receiver has been tested. The tag
320 on the receiver that connects to the USB port should have a P/N that
321 will tell you what type of DMR you have. The UIA-10 type is not
322 supported at this time. This driver maps all buttons to keypress
325 To compile this driver as a module, choose M here: the module will
326 be called keyspan_remote.
328 config USB_APPLETOUCH
329 tristate "Apple USB Touchpad support"
330 depends on USB && INPUT
332 Say Y here if you want to use an Apple USB Touchpad.
334 These are the touchpads that can be found on post-February 2005
335 Apple Powerbooks (prior models have a Synaptics touchpad connected
338 This driver provides a basic mouse driver but can be interfaced
339 with the synaptics X11 driver to provide acceleration and
342 For further information, see
343 <file:Documentation/input/appletouch.txt>.
345 To compile this driver as a module, choose M here: the
346 module will be called appletouch.