2 # USB Input driver configuration
4 comment "USB Human Interface Devices (HID)"
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
17 You can't use this driver and the HIDBP (Boot Protocol) keyboard
18 and mouse drivers at the same time. More information is available:
19 <file:Documentation/input/input.txt>.
23 To compile this driver as a module, choose M here: the
24 module will be called usbhid.
26 comment "Input core support is needed for USB HID input layer or HIDBP support"
27 depends on USB && INPUT=n
30 bool "HID input layer support"
32 depends on INPUT && USB_HID
34 Say Y here if you want to use a USB keyboard, mouse or joystick,
35 or any other HID input device. You also need "Input core support",
36 (CONFIG_INPUT), which you select under "Input device support", above.
41 bool "Force feedback support (EXPERIMENTAL)"
42 depends on USB_HIDINPUT && 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 Devices (Microsoft Sidewinder Force Feedback 2)"
56 Say Y here if you have a PID-compliant joystick and wish to enable force
57 feedback for it. The Microsoft Sidewinder Force Feedback 2 is one such
61 bool "Logitech WingMan *3D support"
64 Say Y here if you have one of these devices:
65 - Logitech WingMan Cordless RumblePad
66 - Logitech WingMan Force 3D
67 and if you want to enable force feedback for them.
68 Note: if you say N here, this device will still be supported, but without
71 config THRUSTMASTER_FF
72 bool "ThrustMaster FireStorm Dual Power 2 support (EXPERIMENTAL)"
73 depends on HID_FF && EXPERIMENTAL
75 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2,
76 and want to enable force feedback support for it.
77 Note: if you say N here, this device will still be supported, but without
81 bool "/dev/hiddev raw HID device support"
84 Say Y here if you want to support HID devices (from the USB
85 specification standpoint) that aren't strictly user interface
86 devices, like monitor controls and Uninterruptable Power Supplies.
88 This module supports these devices separately using a separate
89 event interface on /dev/usb/hiddevX (char 180:96 to 180:111).
90 This driver requires CONFIG_USB_HID.
94 menu "USB HID Boot Protocol drivers"
95 depends on USB!=n && USB_HID!=y
98 tristate "USB HIDBP Keyboard (simple Boot) support"
99 depends on USB && INPUT
101 Say Y here only if you are absolutely sure that you don't want
102 to use the generic HID driver for your USB keyboard and prefer
103 to use the keyboard in its limited Boot Protocol mode instead.
105 This is almost certainly not what you want. This is mostly
106 useful for embedded applications or simple keyboards.
108 To compile this driver as a module, choose M here: the
109 module will be called usbkbd.
111 If even remotely unsure, say N.
114 tristate "USB HIDBP Mouse (simple Boot) support"
115 depends on USB && INPUT
117 Say Y here only if you are absolutely sure that you don't want
118 to use the generic HID driver for your USB mouse and prefer
119 to use the mouse in its limited Boot Protocol mode instead.
121 This is almost certainly not what you want. This is mostly
122 useful for embedded applications or simple mice.
124 To compile this driver as a module, choose M here: the
125 module will be called usbmouse.
127 If even remotely unsure, say N.
132 tristate "Aiptek 6000U/8000U tablet support"
133 depends on USB && INPUT
135 Say Y here if you want to use the USB version of the Aiptek 6000U
136 or Aiptek 8000U tablet. Make sure to say Y to "Mouse support"
137 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
138 (CONFIG_INPUT_EVDEV) as well.
140 To compile this driver as a module, choose M here: the
141 module will be called aiptek.
144 tristate "Wacom Intuos/Graphire tablet support"
145 depends on USB && INPUT
147 Say Y here if you want to use the USB version of the Wacom Intuos
148 or Graphire tablet. Make sure to say Y to "Mouse support"
149 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
150 (CONFIG_INPUT_EVDEV) as well.
152 To compile this driver as a module, choose M here: the
153 module will be called wacom.
156 tristate "KB Gear JamStudio tablet support"
157 depends on USB && INPUT
159 Say Y here if you want to use the USB version of the KB Gear
160 JamStudio tablet. Make sure to say Y to "Mouse support"
161 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
162 (CONFIG_INPUT_EVDEV) as well.
164 To compile this driver as a module, choose M here: the
165 module will be called kbtab.
168 tristate "Griffin PowerMate and Contour Jog support"
169 depends on USB && INPUT
171 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
172 These are aluminum dials which can measure clockwise and anticlockwise
173 rotation. The dial also acts as a pushbutton. The base contains an LED
174 which can be instructed to pulse or to switch to a particular intensity.
176 You can download userspace tools from
177 <http://sowerbutts.com/powermate/>.
179 To compile this driver as a module, choose M here: the
180 module will be called powermate.
183 tristate "MicroTouch USB Touchscreen Driver"
184 depends on USB && INPUT
186 Say Y here if you want to use a MicroTouch (Now 3M) USB
187 Touchscreen controller.
189 See <file:Documentation/usb/mtouch.txt> for additional information.
191 To compile this driver as a module, choose M here: the
192 module will be called mtouchusb.
195 tristate "eGalax TouchKit USB Touchscreen Driver"
196 depends on USB && INPUT
198 Say Y here if you want to use a eGalax TouchKit USB
199 Touchscreen controller.
201 The driver has been tested on a Xenarc 700TSV monitor
202 with eGalax touchscreen.
204 To compile this driver as a module, choose M here: the
205 module will be called touchkitusb.
208 tristate "X-Box gamepad support"
209 depends on USB && INPUT
211 Say Y here if you want to use the X-Box pad with your computer.
212 Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV)
213 and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well.
215 For information about how to connect the X-Box pad to USB, see
216 <file:Documentation/input/xpad.txt>.
218 To compile this driver as a module, choose M here: the
219 module will be called xpad.
221 config USB_ATI_REMOTE
222 tristate "ATI USB RF remote control"
223 depends on USB && INPUT
225 Say Y here if you want to use one of ATI's USB remote controls.
226 These are RF remotes with USB receivers. They come with many of ATI's
227 All-In-Wonder video cards. This driver provides mouse pointer, left
228 and right mouse buttons, and maps all the other remote buttons to
231 To compile this driver as a module, choose M here: the module will be