tjh.dev
Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel
os
linux
1#
2# USB Input driver configuration
3#
4comment "USB Input Devices"
5 depends on USB
6
7config USB_HID
8 tristate "USB Human Interface Device (full HID) support"
9 default y
10 depends on USB && INPUT
11 select HID
12 ---help---
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.
17
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>.
21
22 If unsure, say Y.
23
24 To compile this driver as a module, choose M here: the
25 module will be called usbhid.
26
27comment "Input core support is needed for USB HID input layer or HIDBP support"
28 depends on USB_HID && INPUT=n
29
30config USB_HIDINPUT_POWERBOOK
31 bool "Enable support for iBook/PowerBook special keys"
32 default n
33 depends on USB_HID
34 help
35 Say Y here if you want support for the special keys (Fn, Numlock) on
36 Apple iBooks and PowerBooks.
37
38 If unsure, say N.
39
40config HID_FF
41 bool "Force feedback support (EXPERIMENTAL)"
42 depends on USB_HID && EXPERIMENTAL
43 help
44 Say Y here is you want force feedback support for a few HID devices.
45 See below for a list of supported devices.
46
47 See <file:Documentation/input/ff.txt> for a description of the force
48 feedback API.
49
50 If unsure, say N.
51
52config HID_PID
53 bool "PID device support"
54 depends on HID_FF
55 help
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
58 devices.
59
60config LOGITECH_FF
61 bool "Logitech WingMan *3D support"
62 depends on HID_FF
63 select INPUT_FF_MEMLESS if USB_HID
64 help
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
70 force feedback.
71
72config 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
76 help
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
80 force feedback.
81
82config ZEROPLUS_FF
83 bool "Zeroplus based game controller support"
84 depends on HID_FF
85 select INPUT_FF_MEMLESS if USB_HID
86 help
87 Say Y here if you have a Zeroplus based game controller and want to
88 enable force feedback for it.
89
90config USB_HIDDEV
91 bool "/dev/hiddev raw HID device support"
92 depends on USB_HID
93 help
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.
97
98 This module supports these devices separately using a separate
99 event interface on /dev/usb/hiddevX (char 180:96 to 180:111).
100
101 If unsure, say Y.
102
103menu "USB HID Boot Protocol drivers"
104 depends on USB!=n && USB_HID!=y
105
106config USB_KBD
107 tristate "USB HIDBP Keyboard (simple Boot) support"
108 depends on USB && INPUT
109 ---help---
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.
113
114 This is almost certainly not what you want. This is mostly
115 useful for embedded applications or simple keyboards.
116
117 To compile this driver as a module, choose M here: the
118 module will be called usbkbd.
119
120 If even remotely unsure, say N.
121
122config USB_MOUSE
123 tristate "USB HIDBP Mouse (simple Boot) support"
124 depends on USB && INPUT
125 ---help---
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.
129
130 This is almost certainly not what you want. This is mostly
131 useful for embedded applications or simple mice.
132
133 To compile this driver as a module, choose M here: the
134 module will be called usbmouse.
135
136 If even remotely unsure, say N.
137
138endmenu
139
140config USB_AIPTEK
141 tristate "Aiptek 6000U/8000U tablet support"
142 depends on USB && INPUT
143 help
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.
148
149 To compile this driver as a module, choose M here: the
150 module will be called aiptek.
151
152config USB_WACOM
153 tristate "Wacom Intuos/Graphire tablet support"
154 depends on USB && INPUT
155 help
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.
160
161 To compile this driver as a module, choose M here: the
162 module will be called wacom.
163
164config USB_ACECAD
165 tristate "Acecad Flair tablet support"
166 depends on USB && INPUT
167 help
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.
172
173 To compile this driver as a module, choose M here: the
174 module will be called acecad.
175
176config USB_KBTAB
177 tristate "KB Gear JamStudio tablet support"
178 depends on USB && INPUT
179 help
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.
184
185 To compile this driver as a module, choose M here: the
186 module will be called kbtab.
187
188config USB_POWERMATE
189 tristate "Griffin PowerMate and Contour Jog support"
190 depends on USB && INPUT
191 ---help---
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.
196
197 You can download userspace tools from
198 <http://sowerbutts.com/powermate/>.
199
200 To compile this driver as a module, choose M here: the
201 module will be called powermate.
202
203config USB_TOUCHSCREEN
204 tristate "USB Touchscreen Driver"
205 depends on USB && INPUT
206 ---help---
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)
211 - ITM
212 - some other eTurboTouch
213 - Gunze AHL61
214 - DMC TSC-10/25
215
216 Have a look at <http://linux.chapter7.ch/touchkit/> for
217 a usage description and the required user-space stuff.
218
219 To compile this driver as a module, choose M here: the
220 module will be called usbtouchscreen.
221
222config USB_TOUCHSCREEN_EGALAX
223 default y
224 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EMBEDDED
225 depends on USB_TOUCHSCREEN
226
227config USB_TOUCHSCREEN_PANJIT
228 default y
229 bool "PanJit device support" if EMBEDDED
230 depends on USB_TOUCHSCREEN
231
232config USB_TOUCHSCREEN_3M
233 default y
234 bool "3M/Microtouch EX II series device support" if EMBEDDED
235 depends on USB_TOUCHSCREEN
236
237config USB_TOUCHSCREEN_ITM
238 default y
239 bool "ITM device support" if EMBEDDED
240 depends on USB_TOUCHSCREEN
241
242config USB_TOUCHSCREEN_ETURBO
243 default y
244 bool "eTurboTouch (non-eGalax compatible) device support" if EMBEDDED
245 depends on USB_TOUCHSCREEN
246
247config USB_TOUCHSCREEN_GUNZE
248 default y
249 bool "Gunze AHL61 device support" if EMBEDDED
250 depends on USB_TOUCHSCREEN
251
252config USB_TOUCHSCREEN_DMC_TSC10
253 default y
254 bool "DMC TSC-10/25 device support" if EMBEDDED
255 depends on USB_TOUCHSCREEN
256
257config USB_YEALINK
258 tristate "Yealink usb-p1k voip phone"
259 depends on USB && INPUT && EXPERIMENTAL
260 ---help---
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.
264
265 For information about how to use these additional functions, see
266 <file:Documentation/input/yealink.txt>.
267
268 To compile this driver as a module, choose M here: the module will be
269 called yealink.
270
271config USB_XPAD
272 tristate "X-Box gamepad support"
273 depends on USB && INPUT
274 ---help---
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.
278
279 For information about how to connect the X-Box pad to USB, see
280 <file:Documentation/input/xpad.txt>.
281
282 To compile this driver as a module, choose M here: the
283 module will be called xpad.
284
285config USB_ATI_REMOTE
286 tristate "ATI / X10 USB RF remote control"
287 depends on USB && INPUT
288 ---help---
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.
296
297 To compile this driver as a module, choose M here: the module will be
298 called ati_remote.
299
300config USB_ATI_REMOTE2
301 tristate "ATI / Philips USB RF remote control"
302 depends on USB && INPUT
303 ---help---
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.
310
311 To compile this driver as a module, choose M here: the module will be
312 called ati_remote2.
313
314config USB_KEYSPAN_REMOTE
315 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
316 depends on USB && INPUT && EXPERIMENTAL
317 ---help---
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
323 events.
324
325 To compile this driver as a module, choose M here: the module will
326 be called keyspan_remote.
327
328config USB_APPLETOUCH
329 tristate "Apple USB Touchpad support"
330 depends on USB && INPUT
331 ---help---
332 Say Y here if you want to use an Apple USB Touchpad.
333
334 These are the touchpads that can be found on post-February 2005
335 Apple Powerbooks (prior models have a Synaptics touchpad connected
336 to the ADB bus).
337
338 This driver provides a basic mouse driver but can be interfaced
339 with the synaptics X11 driver to provide acceleration and
340 scrolling in X11.
341
342 For further information, see
343 <file:Documentation/input/appletouch.txt>.
344
345 To compile this driver as a module, choose M here: the
346 module will be called appletouch.