[linux-2.6-block.git] / drivers / usb / input / Kconfig

#
# USB Input driver configuration
#
comment "USB Input Devices"
	depends on USB

config USB_HID
	tristate "USB Human Interface Device (full HID) support"
	depends on USB
	---help---
	  Say Y here if you want full HID support to connect keyboards,
	  mice, joysticks, graphic tablets, or any other HID based devices
	  to your computer via USB. You also need to select HID Input layer
	  support (below) if you want to use keyboards, mice, joysticks and
	  the like ... as well as Uninterruptible Power Supply (UPS) and
	  monitor control devices.

	  You can't use this driver and the HIDBP (Boot Protocol) keyboard
	  and mouse drivers at the same time. More information is available:
	  <file:Documentation/input/input.txt>.

	  If unsure, say Y.

	  To compile this driver as a module, choose M here: the
	  module will be called usbhid.

comment "Input core support is needed for USB HID input layer or HIDBP support"
	depends on USB_HID && INPUT=n

config USB_HIDINPUT
	bool "HID input layer support"
	default y
	depends on INPUT && USB_HID
	help
	  Say Y here if you want to use a USB keyboard, mouse or joystick,
	  or any other HID input device.

	  If unsure, say Y.

config USB_HIDINPUT_POWERBOOK
	bool "Enable support for iBook/PowerBook special keys"
	default n
	depends on USB_HIDINPUT
	help
	  Say Y here if you want support for the special keys (Fn, Numlock) on
	  Apple iBooks and PowerBooks.

	  If unsure, say N.

config HID_FF
	bool "Force feedback support (EXPERIMENTAL)"
	depends on USB_HIDINPUT && EXPERIMENTAL
	help
	  Say Y here is you want force feedback support for a few HID devices.
	  See below for a list of supported devices.

	  See <file:Documentation/input/ff.txt> for a description of the force
	  feedback API.

	  If unsure, say N.

config HID_PID
	bool "PID Devices (Microsoft Sidewinder Force Feedback 2)"
	depends on HID_FF
	help
	  Say Y here if you have a PID-compliant joystick and wish to enable force
	  feedback for it. The Microsoft Sidewinder Force Feedback 2 is one such
	  device.

config LOGITECH_FF
	bool "Logitech WingMan *3D support"
	depends on HID_FF
	help
	  Say Y here if you have one of these devices:
	  - Logitech WingMan Cordless RumblePad
	  - Logitech WingMan Force 3D
	  and if you want to enable force feedback for them.
	  Note: if you say N here, this device will still be supported, but without
	  force feedback.

config THRUSTMASTER_FF
	bool "ThrustMaster FireStorm Dual Power 2 support (EXPERIMENTAL)"
	depends on HID_FF && EXPERIMENTAL
	help
	  Say Y here if you have a THRUSTMASTER FireStore Dual Power 2,
	  and want to enable force feedback support for it.
	  Note: if you say N here, this device will still be supported, but without
	  force feedback.

config USB_HIDDEV
	bool "/dev/hiddev raw HID device support"
	depends on USB_HID
	help
	  Say Y here if you want to support HID devices (from the USB
	  specification standpoint) that aren't strictly user interface
	  devices, like monitor controls and Uninterruptable Power Supplies.

	  This module supports these devices separately using a separate
	  event interface on /dev/usb/hiddevX (char 180:96 to 180:111).

	  If unsure, say Y.

menu "USB HID Boot Protocol drivers"
	depends on USB!=n && USB_HID!=y

config USB_KBD
	tristate "USB HIDBP Keyboard (simple Boot) support"
	depends on USB && INPUT
	---help---
	  Say Y here only if you are absolutely sure that you don't want
	  to use the generic HID driver for your USB keyboard and prefer
	  to use the keyboard in its limited Boot Protocol mode instead.

	  This is almost certainly not what you want.  This is mostly
	  useful for embedded applications or simple keyboards.

	  To compile this driver as a module, choose M here: the
	  module will be called usbkbd.

	  If even remotely unsure, say N.

config USB_MOUSE
	tristate "USB HIDBP Mouse (simple Boot) support"
	depends on USB && INPUT
	---help---
	  Say Y here only if you are absolutely sure that you don't want
	  to use the generic HID driver for your USB mouse and prefer
	  to use the mouse in its limited Boot Protocol mode instead.

	  This is almost certainly not what you want.  This is mostly
	  useful for embedded applications or simple mice.

	  To compile this driver as a module, choose M here: the
	  module will be called usbmouse.

	  If even remotely unsure, say N.

endmenu

config USB_AIPTEK
	tristate "Aiptek 6000U/8000U tablet support"
	depends on USB && INPUT
	help
	  Say Y here if you want to use the USB version of the Aiptek 6000U
	  or Aiptek 8000U tablet.  Make sure to say Y to "Mouse support"
	  (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
	  (CONFIG_INPUT_EVDEV) as well.

	  To compile this driver as a module, choose M here: the
	  module will be called aiptek.

config USB_WACOM
	tristate "Wacom Intuos/Graphire tablet support"
	depends on USB && INPUT
	help
	  Say Y here if you want to use the USB version of the Wacom Intuos
	  or Graphire tablet.  Make sure to say Y to "Mouse support"
	  (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
	  (CONFIG_INPUT_EVDEV) as well.

	  To compile this driver as a module, choose M here: the
	  module will be called wacom.

config USB_ACECAD
	tristate "Acecad Flair tablet support"
	depends on USB && INPUT
	help
	  Say Y here if you want to use the USB version of the Acecad Flair
	  tablet.  Make sure to say Y to "Mouse support"
	  (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
	  (CONFIG_INPUT_EVDEV) as well.

	  To compile this driver as a module, choose M here: the
	  module will be called acecad.

config USB_KBTAB
	tristate "KB Gear JamStudio tablet support"
	depends on USB && INPUT
	help
	  Say Y here if you want to use the USB version of the KB Gear
	  JamStudio tablet.  Make sure to say Y to "Mouse support"
	  (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support"
	  (CONFIG_INPUT_EVDEV) as well.

	  To compile this driver as a module, choose M here: the
	  module will be called kbtab.

config USB_POWERMATE
	tristate "Griffin PowerMate and Contour Jog support"
	depends on USB && INPUT
	---help---
	  Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
	  These are aluminum dials which can measure clockwise and anticlockwise
	  rotation.  The dial also acts as a pushbutton.  The base contains an LED
	  which can be instructed to pulse or to switch to a particular intensity.

	  You can download userspace tools from
	  <http://sowerbutts.com/powermate/>.

	  To compile this driver as a module, choose M here: the
	  module will be called powermate.

config USB_TOUCHSCREEN
	tristate "USB Touchscreen Driver"
	depends on USB && INPUT
	---help---
	  USB Touchscreen driver for:
	  - eGalax Touchkit USB
	  - PanJit TouchSet USB
	  - 3M MicroTouch USB
	  - ITM

	  Have a look at <http://linux.chapter7.ch/touchkit/> for
	  a usage description and the required user-space stuff.

	  To compile this driver as a module, choose M here: the
	  module will be called usbtouchscreen.

config USB_TOUCHSCREEN_EGALAX
	default y
	bool "eGalax device support" if EMBEDDED
	depends on USB_TOUCHSCREEN

config USB_TOUCHSCREEN_PANJIT
	default y
	bool "PanJit device support" if EMBEDDED
	depends on USB_TOUCHSCREEN

config USB_TOUCHSCREEN_3M
	default y
	bool "3M/Microtouch device support" if EMBEDDED
	depends on USB_TOUCHSCREEN

config USB_TOUCHSCREEN_ITM
	default y
	bool "ITM device support" if EMBEDDED
	depends on USB_TOUCHSCREEN

config USB_YEALINK
	tristate "Yealink usb-p1k voip phone"
	depends on USB && INPUT && EXPERIMENTAL
	---help---
	  Say Y here if you want to enable keyboard and LCD functions of the
	  Yealink usb-p1k usb phones. The audio part is enabled by the generic
	  usb sound driver, so you might want to enable that as well.

	  For information about how to use these additional functions, see
	  <file:Documentation/input/yealink.txt>.

	  To compile this driver as a module, choose M here: the module will be
	  called yealink.

config USB_XPAD
	tristate "X-Box gamepad support"
	depends on USB && INPUT
	---help---
	  Say Y here if you want to use the X-Box pad with your computer.
	  Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV)
	  and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well.

	  For information about how to connect the X-Box pad to USB, see
	  <file:Documentation/input/xpad.txt>.

	  To compile this driver as a module, choose M here: the
	  module will be called xpad.
	  
config USB_ATI_REMOTE
	tristate "ATI / X10 USB RF remote control"
	depends on USB && INPUT
	---help---
	  Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
	  These are RF remotes with USB receivers. 
	  The ATI remote comes with many of ATI's All-In-Wonder video cards.
	  The X10 "Lola" remote is available at:
	     <http://www.x10.com/products/lola_sg1.htm>
	  This driver provides mouse pointer, left and right mouse buttons, 
	  and maps all the other remote buttons to keypress events.
	  
	  To compile this driver as a module, choose M here: the module will be
	  called ati_remote.
Commit	Line	Data
1da177e4 LT	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	depends on USB
	10	---help---
	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.
	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
	31	bool "HID input layer support"
	32	default y
	33	depends on INPUT && USB_HID
	34	help
	35	Say Y here if you want to use a USB keyboard, mouse or joystick,
	36	or any other HID input device.
	37
	38	If unsure, say Y.
	39
eab9edd2 MH	40	config USB_HIDINPUT_POWERBOOK
	41	bool "Enable support for iBook/PowerBook special keys"
	42	default n
	43	depends on USB_HIDINPUT
	44	help
	45	Say Y here if you want support for the special keys (Fn, Numlock) on
	46	Apple iBooks and PowerBooks.
	47
	48	If unsure, say N.
	49
1da177e4 LT	50	config HID_FF
	51	bool "Force feedback support (EXPERIMENTAL)"
	52	depends on USB_HIDINPUT && EXPERIMENTAL
	53	help
	54	Say Y here is you want force feedback support for a few HID devices.
	55	See below for a list of supported devices.
	56
	57	See <file:Documentation/input/ff.txt> for a description of the force
	58	feedback API.
	59
	60	If unsure, say N.
	61
	62	config HID_PID
	63	bool "PID Devices (Microsoft Sidewinder Force Feedback 2)"
	64	depends on HID_FF
	65	help
	66	Say Y here if you have a PID-compliant joystick and wish to enable force
	67	feedback for it. The Microsoft Sidewinder Force Feedback 2 is one such
	68	device.
	69
	70	config LOGITECH_FF
	71	bool "Logitech WingMan *3D support"
	72	depends on HID_FF
	73	help
	74	Say Y here if you have one of these devices:
	75	- Logitech WingMan Cordless RumblePad
	76	- Logitech WingMan Force 3D
	77	and if you want to enable force feedback for them.
	78	Note: if you say N here, this device will still be supported, but without
	79	force feedback.
	80
	81	config THRUSTMASTER_FF
	82	bool "ThrustMaster FireStorm Dual Power 2 support (EXPERIMENTAL)"
	83	depends on HID_FF && EXPERIMENTAL
	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 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
	103	menu "USB HID Boot Protocol drivers"
	104	depends on USB!=n && USB_HID!=y
	105
	106	config 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
122	config 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
138	endmenu
139
140	config 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
152	config 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
53880546 SV	164	config 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
1da177e4 LT	176	config 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
	188	config 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
1d3e2023 DR	203	config USB_TOUCHSCREEN
	204	tristate "USB Touchscreen Driver"
	205	depends on USB && INPUT
	206	---help---
	207	USB Touchscreen driver for:
	208	- eGalax Touchkit USB
	209	- PanJit TouchSet USB
	210	- 3M MicroTouch USB
	211	- ITM
	212
	213	Have a look at <http://linux.chapter7.ch/touchkit/> for
	214	a usage description and the required user-space stuff.
	215
	216	To compile this driver as a module, choose M here: the
	217	module will be called usbtouchscreen.
	218
	219	config USB_TOUCHSCREEN_EGALAX
	220	default y
	221	bool "eGalax device support" if EMBEDDED
	222	depends on USB_TOUCHSCREEN
	223
	224	config USB_TOUCHSCREEN_PANJIT
	225	default y
	226	bool "PanJit device support" if EMBEDDED
	227	depends on USB_TOUCHSCREEN
	228
	229	config USB_TOUCHSCREEN_3M
	230	default y
	231	bool "3M/Microtouch device support" if EMBEDDED
	232	depends on USB_TOUCHSCREEN
	233
	234	config USB_TOUCHSCREEN_ITM
	235	default y
	236	bool "ITM device support" if EMBEDDED
	237	depends on USB_TOUCHSCREEN
	238
aca951a2 H	239	config USB_YEALINK
	240	tristate "Yealink usb-p1k voip phone"
	241	depends on USB && INPUT && EXPERIMENTAL
	242	---help---
	243	Say Y here if you want to enable keyboard and LCD functions of the
	244	Yealink usb-p1k usb phones. The audio part is enabled by the generic
	245	usb sound driver, so you might want to enable that as well.
	246
	247	For information about how to use these additional functions, see
	248	<file:Documentation/input/yealink.txt>.
	249
	250	To compile this driver as a module, choose M here: the module will be
	251	called yealink.
	252
1da177e4 LT	253	config USB_XPAD
	254	tristate "X-Box gamepad support"
	255	depends on USB && INPUT
	256	---help---
	257	Say Y here if you want to use the X-Box pad with your computer.
	258	Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV)
	259	and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well.
	260
	261	For information about how to connect the X-Box pad to USB, see
	262	<file:Documentation/input/xpad.txt>.
	263
	264	To compile this driver as a module, choose M here: the
	265	module will be called xpad.
	266
	267	config USB_ATI_REMOTE
	268	tristate "ATI / X10 USB RF remote control"
	269	depends on USB && INPUT
	270	---help---
	271	Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
	272	These are RF remotes with USB receivers.
	273	The ATI remote comes with many of ATI's All-In-Wonder video cards.
	274	The X10 "Lola" remote is available at:
	275	<http://www.x10.com/products/lola_sg1.htm>
	276	This driver provides mouse pointer, left and right mouse buttons,
	277	and maps all the other remote buttons to keypress events.
	278
	279	To compile this driver as a module, choose M here: the module will be
	280	called ati_remote.
	281