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 device support"
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
71 bool "Logitech WingMan *3D support"
73 select INPUT_FF_MEMLESS if USB_HID
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
82 config THRUSTMASTER_FF
83 bool "ThrustMaster FireStorm Dual Power 2 support (EXPERIMENTAL)"
84 depends on HID_FF && EXPERIMENTAL
85 select INPUT_FF_MEMLESS if USB_HID
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
93 bool "/dev/hiddev raw HID device support"
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.
100 This module supports these devices separately using a separate
101 event interface on /dev/usb/hiddevX (char 180:96 to 180:111).
105 menu "USB HID Boot Protocol drivers"
106 depends on USB!=n && USB_HID!=y
109 tristate "USB HIDBP Keyboard (simple Boot) support"
110 depends on USB && INPUT
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.
116 This is almost certainly not what you want. This is mostly
117 useful for embedded applications or simple keyboards.
119 To compile this driver as a module, choose M here: the
120 module will be called usbkbd.
122 If even remotely unsure, say N.
125 tristate "USB HIDBP Mouse (simple Boot) support"
126 depends on USB && INPUT
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.
132 This is almost certainly not what you want. This is mostly
133 useful for embedded applications or simple mice.
135 To compile this driver as a module, choose M here: the
136 module will be called usbmouse.
138 If even remotely unsure, say N.
143 tristate "Aiptek 6000U/8000U tablet support"
144 depends on USB && INPUT
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.
151 To compile this driver as a module, choose M here: the
152 module will be called aiptek.
155 tristate "Wacom Intuos/Graphire tablet support"
156 depends on USB && INPUT
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.
163 To compile this driver as a module, choose M here: the
164 module will be called wacom.
167 tristate "Acecad Flair tablet support"
168 depends on USB && INPUT
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.
175 To compile this driver as a module, choose M here: the
176 module will be called acecad.
179 tristate "KB Gear JamStudio tablet support"
180 depends on USB && INPUT
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.
187 To compile this driver as a module, choose M here: the
188 module will be called kbtab.
191 tristate "Griffin PowerMate and Contour Jog support"
192 depends on USB && INPUT
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.
199 You can download userspace tools from
200 <http://sowerbutts.com/powermate/>.
202 To compile this driver as a module, choose M here: the
203 module will be called powermate.
205 config USB_TOUCHSCREEN
206 tristate "USB Touchscreen Driver"
207 depends on USB && INPUT
209 USB Touchscreen driver for:
210 - eGalax Touchkit USB
211 - PanJit TouchSet USB
215 Have a look at <http://linux.chapter7.ch/touchkit/> for
216 a usage description and the required user-space stuff.
218 To compile this driver as a module, choose M here: the
219 module will be called usbtouchscreen.
221 config USB_TOUCHSCREEN_EGALAX
223 bool "eGalax device support" if EMBEDDED
224 depends on USB_TOUCHSCREEN
226 config USB_TOUCHSCREEN_PANJIT
228 bool "PanJit device support" if EMBEDDED
229 depends on USB_TOUCHSCREEN
231 config USB_TOUCHSCREEN_3M
233 bool "3M/Microtouch device support" if EMBEDDED
234 depends on USB_TOUCHSCREEN
236 config USB_TOUCHSCREEN_ITM
238 bool "ITM device support" if EMBEDDED
239 depends on USB_TOUCHSCREEN
242 tristate "Yealink usb-p1k voip phone"
243 depends on USB && INPUT && EXPERIMENTAL
245 Say Y here if you want to enable keyboard and LCD functions of the
246 Yealink usb-p1k usb phones. The audio part is enabled by the generic
247 usb sound driver, so you might want to enable that as well.
249 For information about how to use these additional functions, see
250 <file:Documentation/input/yealink.txt>.
252 To compile this driver as a module, choose M here: the module will be
256 tristate "X-Box gamepad support"
257 depends on USB && INPUT
259 Say Y here if you want to use the X-Box pad with your computer.
260 Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV)
261 and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well.
263 For information about how to connect the X-Box pad to USB, see
264 <file:Documentation/input/xpad.txt>.
266 To compile this driver as a module, choose M here: the
267 module will be called xpad.
269 config USB_ATI_REMOTE
270 tristate "ATI / X10 USB RF remote control"
271 depends on USB && INPUT
273 Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
274 These are RF remotes with USB receivers.
275 The ATI remote comes with many of ATI's All-In-Wonder video cards.
276 The X10 "Lola" remote is available at:
277 <http://www.x10.com/products/lola_sg1.htm>
278 This driver provides mouse pointer, left and right mouse buttons,
279 and maps all the other remote buttons to keypress events.
281 To compile this driver as a module, choose M here: the module will be
284 config USB_ATI_REMOTE2
285 tristate "ATI / Philips USB RF remote control"
286 depends on USB && INPUT
288 Say Y here if you want to use an ATI or Philips USB RF remote control.
289 These are RF remotes with USB receivers.
290 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
291 and is also available as a separate product.
292 This driver provides mouse pointer, left and right mouse buttons,
293 and maps all the other remote buttons to keypress events.
295 To compile this driver as a module, choose M here: the module will be
298 config USB_KEYSPAN_REMOTE
299 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
300 depends on USB && INPUT && EXPERIMENTAL
302 Say Y here if you want to use a Keyspan DMR USB remote control.
303 Currently only the UIA-11 type of receiver has been tested. The tag
304 on the receiver that connects to the USB port should have a P/N that
305 will tell you what type of DMR you have. The UIA-10 type is not
306 supported at this time. This driver maps all buttons to keypress
309 To compile this driver as a module, choose M here: the module will
310 be called keyspan_remote.
312 config USB_APPLETOUCH
313 tristate "Apple USB Touchpad support"
314 depends on USB && INPUT
316 Say Y here if you want to use an Apple USB Touchpad.
318 These are the touchpads that can be found on post-February 2005
319 Apple Powerbooks (prior models have a Synaptics touchpad connected
322 This driver provides a basic mouse driver but can be interfaced
323 with the synaptics X11 driver to provide acceleration and
326 For further information, see
327 <file:Documentation/input/appletouch.txt>.
329 To compile this driver as a module, choose M here: the
330 module will be called appletouch.