2 # USB Input driver configuration
4 comment "USB Input Devices"
8 tristate "USB Human Interface Device (full HID) support"
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.
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
31 bool "HID input layer support"
33 depends on INPUT && USB_HID
35 Say Y here if you want to use a USB keyboard, mouse or joystick,
36 or any other HID input device.
40 config USB_HIDINPUT_POWERBOOK
41 bool "Enable support for iBook/PowerBook special keys"
43 depends on USB_HIDINPUT
45 Say Y here if you want support for the special keys (Fn, Numlock) on
46 Apple iBooks and PowerBooks.
51 bool "Force feedback support (EXPERIMENTAL)"
52 depends on USB_HIDINPUT && EXPERIMENTAL
54 Say Y here is you want force feedback support for a few HID devices.
55 See below for a list of supported devices.
57 See <file:Documentation/input/ff.txt> for a description of the force
63 bool "PID Devices (Microsoft Sidewinder Force Feedback 2)"
66 Say Y here if you have a PID-compliant joystick and wish to enable force
67 feedback for it. The Microsoft Sidewinder Force Feedback 2 is one such
71 bool "Logitech WingMan *3D support"
74 Say Y here if you have one of these devices:
75 - Logitech WingMan Cordless RumblePad
76 - Logitech WingMan Force 3D
77 and if you want to enable force feedback for them.
78 Note: if you say N here, this device will still be supported, but without
81 config THRUSTMASTER_FF
82 bool "ThrustMaster FireStorm Dual Power 2 support (EXPERIMENTAL)"
83 depends on HID_FF && EXPERIMENTAL
85 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2,
86 and want to enable force feedback support for it.
87 Note: if you say N here, this device will still be supported, but without
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.
204 tristate "MicroTouch USB Touchscreen Driver"
205 depends on USB && INPUT
207 Say Y here if you want to use a MicroTouch (Now 3M) USB
208 Touchscreen controller.
210 See <file:Documentation/usb/mtouch.txt> for additional information.
212 To compile this driver as a module, choose M here: the
213 module will be called mtouchusb.
216 tristate "ITM Touch USB Touchscreen Driver"
217 depends on USB && INPUT
219 Say Y here if you want to use a ITM Touch USB
220 Touchscreen controller.
222 This touchscreen is used in LG 1510SF monitors.
224 To compile this driver as a module, choose M here: the
225 module will be called itmtouch.
228 tristate "eGalax TouchKit USB Touchscreen Driver"
229 depends on USB && INPUT
231 Say Y here if you want to use a eGalax TouchKit USB
232 Touchscreen controller.
234 The driver has been tested on a Xenarc 700TSV monitor
235 with eGalax touchscreen.
237 Have a look at <http://linux.chapter7.ch/touchkit/> for
238 a usage description and the required user-space stuff.
240 To compile this driver as a module, choose M here: the
241 module will be called touchkitusb.
244 tristate "Yealink usb-p1k voip phone"
245 depends on USB && INPUT && EXPERIMENTAL
247 Say Y here if you want to enable keyboard and LCD functions of the
248 Yealink usb-p1k usb phones. The audio part is enabled by the generic
249 usb sound driver, so you might want to enable that as well.
251 For information about how to use these additional functions, see
252 <file:Documentation/input/yealink.txt>.
254 To compile this driver as a module, choose M here: the module will be
258 tristate "X-Box gamepad support"
259 depends on USB && INPUT
261 Say Y here if you want to use the X-Box pad with your computer.
262 Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV)
263 and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well.
265 For information about how to connect the X-Box pad to USB, see
266 <file:Documentation/input/xpad.txt>.
268 To compile this driver as a module, choose M here: the
269 module will be called xpad.
271 config USB_ATI_REMOTE
272 tristate "ATI / X10 USB RF remote control"
273 depends on USB && INPUT
275 Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
276 These are RF remotes with USB receivers.
277 The ATI remote comes with many of ATI's All-In-Wonder video cards.
278 The X10 "Lola" remote is available at:
279 <http://www.x10.com/products/lola_sg1.htm>
280 This driver provides mouse pointer, left and right mouse buttons,
281 and maps all the other remote buttons to keypress events.
283 To compile this driver as a module, choose M here: the module will be
286 config USB_ATI_REMOTE2
287 tristate "ATI / Philips USB RF remote control"
288 depends on USB && INPUT
290 Say Y here if you want to use an ATI or Philips USB RF remote control.
291 These are RF remotes with USB receivers.
292 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
293 and is also available as a separate product.
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_KEYSPAN_REMOTE
301 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
302 depends on USB && INPUT && EXPERIMENTAL
304 Say Y here if you want to use a Keyspan DMR USB remote control.
305 Currently only the UIA-11 type of receiver has been tested. The tag
306 on the receiver that connects to the USB port should have a P/N that
307 will tell you what type of DMR you have. The UIA-10 type is not
308 supported at this time. This driver maps all buttons to keypress
311 To compile this driver as a module, choose M here: the module will
312 be called keyspan_remote.
314 config USB_APPLETOUCH
315 tristate "Apple USB Touchpad support"
316 depends on USB && INPUT
318 Say Y here if you want to use an Apple USB Touchpad.
320 These are the touchpads that can be found on post-February 2005
321 Apple Powerbooks (prior models have a Synaptics touchpad connected
324 This driver provides a basic mouse driver but can be interfaced
325 with the synaptics X11 driver to provide acceleration and
328 For further information, see
329 <file:Documentation/input/appletouch.txt>.
331 To compile this driver as a module, choose M here: the
332 module will be called appletouch.