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 "Zeroplus based game controller support"
95 select INPUT_FF_MEMLESS if USB_HID
97 Say Y here if you have a Zeroplus based game controller and want to
98 enable force feedback for it.
101 bool "/dev/hiddev raw HID device support"
104 Say Y here if you want to support HID devices (from the USB
105 specification standpoint) that aren't strictly user interface
106 devices, like monitor controls and Uninterruptable Power Supplies.
108 This module supports these devices separately using a separate
109 event interface on /dev/usb/hiddevX (char 180:96 to 180:111).
113 menu "USB HID Boot Protocol drivers"
114 depends on USB!=n && USB_HID!=y
117 tristate "USB HIDBP Keyboard (simple Boot) support"
118 depends on USB && INPUT
120 Say Y here only if you are absolutely sure that you don't want
121 to use the generic HID driver for your USB keyboard and prefer
122 to use the keyboard in its limited Boot Protocol mode instead.
124 This is almost certainly not what you want. This is mostly
125 useful for embedded applications or simple keyboards.
127 To compile this driver as a module, choose M here: the
128 module will be called usbkbd.
130 If even remotely unsure, say N.
133 tristate "USB HIDBP Mouse (simple Boot) support"
134 depends on USB && INPUT
136 Say Y here only if you are absolutely sure that you don't want
137 to use the generic HID driver for your USB mouse and prefer
138 to use the mouse in its limited Boot Protocol mode instead.
140 This is almost certainly not what you want. This is mostly
141 useful for embedded applications or simple mice.
143 To compile this driver as a module, choose M here: the
144 module will be called usbmouse.
146 If even remotely unsure, say N.
151 tristate "Aiptek 6000U/8000U tablet support"
152 depends on USB && INPUT
154 Say Y here if you want to use the USB version of the Aiptek 6000U
155 or Aiptek 8000U tablet. Make sure to say Y to "Mouse support"
156 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
157 (CONFIG_INPUT_EVDEV) as well.
159 To compile this driver as a module, choose M here: the
160 module will be called aiptek.
163 tristate "Wacom Intuos/Graphire tablet support"
164 depends on USB && INPUT
166 Say Y here if you want to use the USB version of the Wacom Intuos
167 or Graphire tablet. Make sure to say Y to "Mouse support"
168 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
169 (CONFIG_INPUT_EVDEV) as well.
171 To compile this driver as a module, choose M here: the
172 module will be called wacom.
175 tristate "Acecad Flair tablet support"
176 depends on USB && INPUT
178 Say Y here if you want to use the USB version of the Acecad Flair
179 tablet. Make sure to say Y to "Mouse support"
180 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
181 (CONFIG_INPUT_EVDEV) as well.
183 To compile this driver as a module, choose M here: the
184 module will be called acecad.
187 tristate "KB Gear JamStudio tablet support"
188 depends on USB && INPUT
190 Say Y here if you want to use the USB version of the KB Gear
191 JamStudio tablet. Make sure to say Y to "Mouse support"
192 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
193 (CONFIG_INPUT_EVDEV) as well.
195 To compile this driver as a module, choose M here: the
196 module will be called kbtab.
199 tristate "Griffin PowerMate and Contour Jog support"
200 depends on USB && INPUT
202 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
203 These are aluminum dials which can measure clockwise and anticlockwise
204 rotation. The dial also acts as a pushbutton. The base contains an LED
205 which can be instructed to pulse or to switch to a particular intensity.
207 You can download userspace tools from
208 <http://sowerbutts.com/powermate/>.
210 To compile this driver as a module, choose M here: the
211 module will be called powermate.
213 config USB_TOUCHSCREEN
214 tristate "USB Touchscreen Driver"
215 depends on USB && INPUT
217 USB Touchscreen driver for:
218 - eGalax Touchkit USB
219 - PanJit TouchSet USB
223 Have a look at <http://linux.chapter7.ch/touchkit/> for
224 a usage description and the required user-space stuff.
226 To compile this driver as a module, choose M here: the
227 module will be called usbtouchscreen.
229 config USB_TOUCHSCREEN_EGALAX
231 bool "eGalax device support" if EMBEDDED
232 depends on USB_TOUCHSCREEN
234 config USB_TOUCHSCREEN_PANJIT
236 bool "PanJit device support" if EMBEDDED
237 depends on USB_TOUCHSCREEN
239 config USB_TOUCHSCREEN_3M
241 bool "3M/Microtouch device support" if EMBEDDED
242 depends on USB_TOUCHSCREEN
244 config USB_TOUCHSCREEN_ITM
246 bool "ITM device support" if EMBEDDED
247 depends on USB_TOUCHSCREEN
250 tristate "Yealink usb-p1k voip phone"
251 depends on USB && INPUT && EXPERIMENTAL
253 Say Y here if you want to enable keyboard and LCD functions of the
254 Yealink usb-p1k usb phones. The audio part is enabled by the generic
255 usb sound driver, so you might want to enable that as well.
257 For information about how to use these additional functions, see
258 <file:Documentation/input/yealink.txt>.
260 To compile this driver as a module, choose M here: the module will be
264 tristate "X-Box gamepad support"
265 depends on USB && INPUT
267 Say Y here if you want to use the X-Box pad with your computer.
268 Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV)
269 and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well.
271 For information about how to connect the X-Box pad to USB, see
272 <file:Documentation/input/xpad.txt>.
274 To compile this driver as a module, choose M here: the
275 module will be called xpad.
277 config USB_ATI_REMOTE
278 tristate "ATI / X10 USB RF remote control"
279 depends on USB && INPUT
281 Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
282 These are RF remotes with USB receivers.
283 The ATI remote comes with many of ATI's All-In-Wonder video cards.
284 The X10 "Lola" remote is available at:
285 <http://www.x10.com/products/lola_sg1.htm>
286 This driver provides mouse pointer, left and right mouse buttons,
287 and maps all the other remote buttons to keypress events.
289 To compile this driver as a module, choose M here: the module will be
292 config USB_ATI_REMOTE2
293 tristate "ATI / Philips USB RF remote control"
294 depends on USB && INPUT
296 Say Y here if you want to use an ATI or Philips USB RF remote control.
297 These are RF remotes with USB receivers.
298 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
299 and is also available as a separate product.
300 This driver provides mouse pointer, left and right mouse buttons,
301 and maps all the other remote buttons to keypress events.
303 To compile this driver as a module, choose M here: the module will be
306 config USB_KEYSPAN_REMOTE
307 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
308 depends on USB && INPUT && EXPERIMENTAL
310 Say Y here if you want to use a Keyspan DMR USB remote control.
311 Currently only the UIA-11 type of receiver has been tested. The tag
312 on the receiver that connects to the USB port should have a P/N that
313 will tell you what type of DMR you have. The UIA-10 type is not
314 supported at this time. This driver maps all buttons to keypress
317 To compile this driver as a module, choose M here: the module will
318 be called keyspan_remote.
320 config USB_APPLETOUCH
321 tristate "Apple USB Touchpad support"
322 depends on USB && INPUT
324 Say Y here if you want to use an Apple USB Touchpad.
326 These are the touchpads that can be found on post-February 2005
327 Apple Powerbooks (prior models have a Synaptics touchpad connected
330 This driver provides a basic mouse driver but can be interfaced
331 with the synaptics X11 driver to provide acceleration and
334 For further information, see
335 <file:Documentation/input/appletouch.txt>.
337 To compile this driver as a module, choose M here: the
338 module will be called appletouch.