hid: force feedback driver for PantherLord USB/PS2 2in1 Adapter
[deliverable/linux.git] / drivers / usb / input / Kconfig
1 #
2 # USB Input driver configuration
3 #
4 comment "USB Input Devices"
5 depends on USB
6
7 config 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
27 comment "Input core support is needed for USB HID input layer or HIDBP support"
28 depends on USB_HID && INPUT=n
29
30 config 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
40 config 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
52 config 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
60 config 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
72 config PANTHERLORD_FF
73 bool "PantherLord USB/PS2 2in1 Adapter support"
74 depends on HID_FF
75 select INPUT_FF_MEMLESS if USB_HID
76 help
77 Say Y here if you have a PantherLord USB/PS2 2in1 Adapter and want
78 to enable force feedback support for it.
79
80 config THRUSTMASTER_FF
81 bool "ThrustMaster FireStorm Dual Power 2 support (EXPERIMENTAL)"
82 depends on HID_FF && EXPERIMENTAL
83 select INPUT_FF_MEMLESS if USB_HID
84 help
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
88 force feedback.
89
90 config ZEROPLUS_FF
91 bool "Zeroplus based game controller support"
92 depends on HID_FF
93 select INPUT_FF_MEMLESS if USB_HID
94 help
95 Say Y here if you have a Zeroplus based game controller and want to
96 enable force feedback for it.
97
98 config USB_HIDDEV
99 bool "/dev/hiddev raw HID device support"
100 depends on USB_HID
101 help
102 Say Y here if you want to support HID devices (from the USB
103 specification standpoint) that aren't strictly user interface
104 devices, like monitor controls and Uninterruptable Power Supplies.
105
106 This module supports these devices separately using a separate
107 event interface on /dev/usb/hiddevX (char 180:96 to 180:111).
108
109 If unsure, say Y.
110
111 menu "USB HID Boot Protocol drivers"
112 depends on USB!=n && USB_HID!=y
113
114 config USB_KBD
115 tristate "USB HIDBP Keyboard (simple Boot) support"
116 depends on USB && INPUT
117 ---help---
118 Say Y here only if you are absolutely sure that you don't want
119 to use the generic HID driver for your USB keyboard and prefer
120 to use the keyboard in its limited Boot Protocol mode instead.
121
122 This is almost certainly not what you want. This is mostly
123 useful for embedded applications or simple keyboards.
124
125 To compile this driver as a module, choose M here: the
126 module will be called usbkbd.
127
128 If even remotely unsure, say N.
129
130 config USB_MOUSE
131 tristate "USB HIDBP Mouse (simple Boot) support"
132 depends on USB && INPUT
133 ---help---
134 Say Y here only if you are absolutely sure that you don't want
135 to use the generic HID driver for your USB mouse and prefer
136 to use the mouse in its limited Boot Protocol mode instead.
137
138 This is almost certainly not what you want. This is mostly
139 useful for embedded applications or simple mice.
140
141 To compile this driver as a module, choose M here: the
142 module will be called usbmouse.
143
144 If even remotely unsure, say N.
145
146 endmenu
147
148 config USB_AIPTEK
149 tristate "Aiptek 6000U/8000U tablet support"
150 depends on USB && INPUT
151 help
152 Say Y here if you want to use the USB version of the Aiptek 6000U
153 or Aiptek 8000U tablet. Make sure to say Y to "Mouse support"
154 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
155 (CONFIG_INPUT_EVDEV) as well.
156
157 To compile this driver as a module, choose M here: the
158 module will be called aiptek.
159
160 config USB_WACOM
161 tristate "Wacom Intuos/Graphire tablet support"
162 depends on USB && INPUT
163 help
164 Say Y here if you want to use the USB version of the Wacom Intuos
165 or Graphire tablet. Make sure to say Y to "Mouse support"
166 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
167 (CONFIG_INPUT_EVDEV) as well.
168
169 To compile this driver as a module, choose M here: the
170 module will be called wacom.
171
172 config USB_ACECAD
173 tristate "Acecad Flair tablet support"
174 depends on USB && INPUT
175 help
176 Say Y here if you want to use the USB version of the Acecad Flair
177 tablet. Make sure to say Y to "Mouse support"
178 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
179 (CONFIG_INPUT_EVDEV) as well.
180
181 To compile this driver as a module, choose M here: the
182 module will be called acecad.
183
184 config USB_KBTAB
185 tristate "KB Gear JamStudio tablet support"
186 depends on USB && INPUT
187 help
188 Say Y here if you want to use the USB version of the KB Gear
189 JamStudio tablet. Make sure to say Y to "Mouse support"
190 (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
191 (CONFIG_INPUT_EVDEV) as well.
192
193 To compile this driver as a module, choose M here: the
194 module will be called kbtab.
195
196 config USB_POWERMATE
197 tristate "Griffin PowerMate and Contour Jog support"
198 depends on USB && INPUT
199 ---help---
200 Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
201 These are aluminum dials which can measure clockwise and anticlockwise
202 rotation. The dial also acts as a pushbutton. The base contains an LED
203 which can be instructed to pulse or to switch to a particular intensity.
204
205 You can download userspace tools from
206 <http://sowerbutts.com/powermate/>.
207
208 To compile this driver as a module, choose M here: the
209 module will be called powermate.
210
211 config USB_TOUCHSCREEN
212 tristate "USB Touchscreen Driver"
213 depends on USB && INPUT
214 ---help---
215 USB Touchscreen driver for:
216 - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700)
217 - PanJit TouchSet USB
218 - 3M MicroTouch USB (EX II series)
219 - ITM
220 - some other eTurboTouch
221 - Gunze AHL61
222 - DMC TSC-10/25
223
224 Have a look at <http://linux.chapter7.ch/touchkit/> for
225 a usage description and the required user-space stuff.
226
227 To compile this driver as a module, choose M here: the
228 module will be called usbtouchscreen.
229
230 config USB_TOUCHSCREEN_EGALAX
231 default y
232 bool "eGalax, eTurboTouch CT-410/510/700 device support" if EMBEDDED
233 depends on USB_TOUCHSCREEN
234
235 config USB_TOUCHSCREEN_PANJIT
236 default y
237 bool "PanJit device support" if EMBEDDED
238 depends on USB_TOUCHSCREEN
239
240 config USB_TOUCHSCREEN_3M
241 default y
242 bool "3M/Microtouch EX II series device support" if EMBEDDED
243 depends on USB_TOUCHSCREEN
244
245 config USB_TOUCHSCREEN_ITM
246 default y
247 bool "ITM device support" if EMBEDDED
248 depends on USB_TOUCHSCREEN
249
250 config USB_TOUCHSCREEN_ETURBO
251 default y
252 bool "eTurboTouch (non-eGalax compatible) device support" if EMBEDDED
253 depends on USB_TOUCHSCREEN
254
255 config USB_TOUCHSCREEN_GUNZE
256 default y
257 bool "Gunze AHL61 device support" if EMBEDDED
258 depends on USB_TOUCHSCREEN
259
260 config USB_TOUCHSCREEN_DMC_TSC10
261 default y
262 bool "DMC TSC-10/25 device support" if EMBEDDED
263 depends on USB_TOUCHSCREEN
264
265 config USB_YEALINK
266 tristate "Yealink usb-p1k voip phone"
267 depends on USB && INPUT && EXPERIMENTAL
268 ---help---
269 Say Y here if you want to enable keyboard and LCD functions of the
270 Yealink usb-p1k usb phones. The audio part is enabled by the generic
271 usb sound driver, so you might want to enable that as well.
272
273 For information about how to use these additional functions, see
274 <file:Documentation/input/yealink.txt>.
275
276 To compile this driver as a module, choose M here: the module will be
277 called yealink.
278
279 config USB_XPAD
280 tristate "X-Box gamepad support"
281 depends on USB && INPUT
282 ---help---
283 Say Y here if you want to use the X-Box pad with your computer.
284 Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV)
285 and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well.
286
287 For information about how to connect the X-Box pad to USB, see
288 <file:Documentation/input/xpad.txt>.
289
290 To compile this driver as a module, choose M here: the
291 module will be called xpad.
292
293 config USB_ATI_REMOTE
294 tristate "ATI / X10 USB RF remote control"
295 depends on USB && INPUT
296 ---help---
297 Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
298 These are RF remotes with USB receivers.
299 The ATI remote comes with many of ATI's All-In-Wonder video cards.
300 The X10 "Lola" remote is available at:
301 <http://www.x10.com/products/lola_sg1.htm>
302 This driver provides mouse pointer, left and right mouse buttons,
303 and maps all the other remote buttons to keypress events.
304
305 To compile this driver as a module, choose M here: the module will be
306 called ati_remote.
307
308 config USB_ATI_REMOTE2
309 tristate "ATI / Philips USB RF remote control"
310 depends on USB && INPUT
311 ---help---
312 Say Y here if you want to use an ATI or Philips USB RF remote control.
313 These are RF remotes with USB receivers.
314 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
315 and is also available as a separate product.
316 This driver provides mouse pointer, left and right mouse buttons,
317 and maps all the other remote buttons to keypress events.
318
319 To compile this driver as a module, choose M here: the module will be
320 called ati_remote2.
321
322 config USB_KEYSPAN_REMOTE
323 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
324 depends on USB && INPUT && EXPERIMENTAL
325 ---help---
326 Say Y here if you want to use a Keyspan DMR USB remote control.
327 Currently only the UIA-11 type of receiver has been tested. The tag
328 on the receiver that connects to the USB port should have a P/N that
329 will tell you what type of DMR you have. The UIA-10 type is not
330 supported at this time. This driver maps all buttons to keypress
331 events.
332
333 To compile this driver as a module, choose M here: the module will
334 be called keyspan_remote.
335
336 config USB_APPLETOUCH
337 tristate "Apple USB Touchpad support"
338 depends on USB && INPUT
339 ---help---
340 Say Y here if you want to use an Apple USB Touchpad.
341
342 These are the touchpads that can be found on post-February 2005
343 Apple Powerbooks (prior models have a Synaptics touchpad connected
344 to the ADB bus).
345
346 This driver provides a basic mouse driver but can be interfaced
347 with the synaptics X11 driver to provide acceleration and
348 scrolling in X11.
349
350 For further information, see
351 <file:Documentation/input/appletouch.txt>.
352
353 To compile this driver as a module, choose M here: the
354 module will be called appletouch.
This page took 0.051552 seconds and 5 git commands to generate.