[net-next-2.6.git] / drivers / input / Kconfig

#
# Input device configuration
#

menu "Input device support"
	depends on !S390

config INPUT
	tristate "Generic input layer (needed for keyboard, mouse, ...)" if EMBEDDED
	default y
	---help---
	  Say Y here if you have any input device (mouse, keyboard, tablet,
	  joystick, steering wheel ...) connected to your system and want
	  it to be available to applications. This includes standard PS/2
	  keyboard and mouse.

	  Say N here if you have a headless (no monitor, no keyboard) system.

	  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 input.

if INPUT

config INPUT_FF_MEMLESS
	tristate "Support for memoryless force-feedback devices"
	default n
	---help---
	  Say Y here if you have memoryless force-feedback input device
	  such as Logitech WingMan Force 3D, ThrustMaster FireStorm Dual
	  Power 2, or similar. You will also need to enable hardware-specific
	  driver.

	  If unsure, say N.

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

config INPUT_POLLDEV
	tristate "Polled input device skeleton"
	help
	  Say Y here if you are using a driver for an input
	  device that periodically polls hardware state. This
	  option is only useful for out-of-tree drivers since
	  in-tree drivers select it automatically.

	  If unsure, say N.

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

comment "Userland interfaces"

config INPUT_MOUSEDEV
	tristate "Mouse interface" if EMBEDDED
	default y
	---help---
	  Say Y here if you want your mouse to be accessible as char devices
	  13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice as an
	  emulated IntelliMouse Explorer PS/2 mouse. That way, all user space
	  programs (including SVGAlib, GPM and X) will be able to use your
	  mouse.

	  If unsure, say Y.

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

config INPUT_MOUSEDEV_PSAUX
	bool "Provide legacy /dev/psaux device"
	default y
	depends on INPUT_MOUSEDEV
	---help---
	  Say Y here if you want your mouse also be accessible as char device
	  10:1 - /dev/psaux. The data available through /dev/psaux is exactly
	  the same as the data from /dev/input/mice.

	  If unsure, say Y.


config INPUT_MOUSEDEV_SCREEN_X
	int "Horizontal screen resolution"
	depends on INPUT_MOUSEDEV
	default "1024"
	help
	  If you're using a digitizer, or a graphic tablet, and want to use
	  it as a mouse then the mousedev driver needs to know the X window
	  screen resolution you are using to correctly scale the data. If
	  you're not using a digitizer, this value is ignored.

config INPUT_MOUSEDEV_SCREEN_Y
	int "Vertical screen resolution"
	depends on INPUT_MOUSEDEV
	default "768"
	help
	  If you're using a digitizer, or a graphic tablet, and want to use
	  it as a mouse then the mousedev driver needs to know the X window
	  screen resolution you are using to correctly scale the data. If
	  you're not using a digitizer, this value is ignored.

config INPUT_JOYDEV
	tristate "Joystick interface"
	---help---
	  Say Y here if you want your joystick or gamepad to be
	  accessible as char device 13:0+ - /dev/input/jsX device.

	  If unsure, say Y.

	  More information is available: <file:Documentation/input/joystick.txt>

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

config INPUT_EVDEV
	tristate "Event interface"
	help
	  Say Y here if you want your input device events be accessible
	  under char device 13:64+ - /dev/input/eventX in a generic way.

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

config INPUT_EVBUG
	tristate "Event debugging"
	---help---
	  Say Y here if you have a problem with the input subsystem and
	  want all events (keypresses, mouse movements), to be output to
	  the system log. While this is useful for debugging, it's also
	  a security threat - your keypresses include your passwords, of
	  course.

	  If unsure, say N.

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

config INPUT_APMPOWER
	tristate "Input Power Event -> APM Bridge" if EMBEDDED
	depends on INPUT && APM_EMULATION
	---help---
	  Say Y here if you want suspend key events to trigger a user
	  requested suspend through APM. This is useful on embedded
	  systems where such behaviour is desired without userspace
	  interaction. If unsure, say N.

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

config XEN_KBDDEV_FRONTEND
	tristate "Xen virtual keyboard and mouse support"
	depends on XEN_FBDEV_FRONTEND
	default y
	help
	  This driver implements the front-end of the Xen virtual
	  keyboard and mouse device driver.  It communicates with a back-end
	  in another domain.

comment "Input Device Drivers"

source "drivers/input/keyboard/Kconfig"

source "drivers/input/mouse/Kconfig"

source "drivers/input/joystick/Kconfig"

source "drivers/input/tablet/Kconfig"

source "drivers/input/touchscreen/Kconfig"

source "drivers/input/misc/Kconfig"

endif

menu "Hardware I/O ports"

source "drivers/input/serio/Kconfig"

source "drivers/input/gameport/Kconfig"

endmenu

endmenu
Commit	Line	Data
1da177e4 LT	1	#
	2	# Input device configuration
	3	#
	4
	5	menu "Input device support"
9556fb73	6	depends on !S390
1da177e4 LT	7
	8	config INPUT
	9	tristate "Generic input layer (needed for keyboard, mouse, ...)" if EMBEDDED
	10	default y
	11	---help---
	12	Say Y here if you have any input device (mouse, keyboard, tablet,
	13	joystick, steering wheel ...) connected to your system and want
	14	it to be available to applications. This includes standard PS/2
	15	keyboard and mouse.
	16
	17	Say N here if you have a headless (no monitor, no keyboard) system.
	18
	19	More information is available: <file:Documentation/input/input.txt>
	20
	21	If unsure, say Y.
	22
	23	To compile this driver as a module, choose M here: the
	24	module will be called input.
	25
	26	if INPUT
	27
7d928a2b AH	28	config INPUT_FF_MEMLESS
	29	tristate "Support for memoryless force-feedback devices"
	30	default n
	31	---help---
	32	Say Y here if you have memoryless force-feedback input device
	33	such as Logitech WingMan Force 3D, ThrustMaster FireStorm Dual
	34	Power 2, or similar. You will also need to enable hardware-specific
	35	driver.
	36
	37	If unsure, say N.
	38
	39	To compile this driver as a module, choose M here: the
	40	module will be called ff-memless.
	41
893e7c2d DT	42	config INPUT_POLLDEV
	43	tristate "Polled input device skeleton"
	44	help
	45	Say Y here if you are using a driver for an input
	46	device that periodically polls hardware state. This
	47	option is only useful for out-of-tree drivers since
	48	in-tree drivers select it automatically.
	49
	50	If unsure, say N.
	51
	52	To compile this driver as a module, choose M here: the
	53	module will be called input-polldev.
	54
1da177e4 LT	55	comment "Userland interfaces"
	56
	57	config INPUT_MOUSEDEV
	58	tristate "Mouse interface" if EMBEDDED
	59	default y
	60	---help---
	61	Say Y here if you want your mouse to be accessible as char devices
	62	13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice as an
	63	emulated IntelliMouse Explorer PS/2 mouse. That way, all user space
	64	programs (including SVGAlib, GPM and X) will be able to use your
	65	mouse.
	66
	67	If unsure, say Y.
	68
	69	To compile this driver as a module, choose M here: the
	70	module will be called mousedev.
	71
	72	config INPUT_MOUSEDEV_PSAUX
	73	bool "Provide legacy /dev/psaux device"
	74	default y
	75	depends on INPUT_MOUSEDEV
	76	---help---
	77	Say Y here if you want your mouse also be accessible as char device
	78	10:1 - /dev/psaux. The data available through /dev/psaux is exactly
	79	the same as the data from /dev/input/mice.
	80
	81	If unsure, say Y.
	82
	83
	84	config INPUT_MOUSEDEV_SCREEN_X
	85	int "Horizontal screen resolution"
	86	depends on INPUT_MOUSEDEV
	87	default "1024"
	88	help
	89	If you're using a digitizer, or a graphic tablet, and want to use
	90	it as a mouse then the mousedev driver needs to know the X window
	91	screen resolution you are using to correctly scale the data. If
	92	you're not using a digitizer, this value is ignored.
	93
	94	config INPUT_MOUSEDEV_SCREEN_Y
	95	int "Vertical screen resolution"
	96	depends on INPUT_MOUSEDEV
	97	default "768"
	98	help
	99	If you're using a digitizer, or a graphic tablet, and want to use
	100	it as a mouse then the mousedev driver needs to know the X window
	101	screen resolution you are using to correctly scale the data. If
	102	you're not using a digitizer, this value is ignored.
	103
	104	config INPUT_JOYDEV
	105	tristate "Joystick interface"
	106	---help---
	107	Say Y here if you want your joystick or gamepad to be
	108	accessible as char device 13:0+ - /dev/input/jsX device.
	109
	110	If unsure, say Y.
	111
	112	More information is available: <file:Documentation/input/joystick.txt>
	113
	114	To compile this driver as a module, choose M here: the
	115	module will be called joydev.
	116
1da177e4 LT	117	config INPUT_EVDEV
	118	tristate "Event interface"
	119	help
	120	Say Y here if you want your input device events be accessible
	121	under char device 13:64+ - /dev/input/eventX in a generic way.
	122
	123	To compile this driver as a module, choose M here: the
	124	module will be called evdev.
	125
	126	config INPUT_EVBUG
	127	tristate "Event debugging"
	128	---help---
	129	Say Y here if you have a problem with the input subsystem and
	130	want all events (keypresses, mouse movements), to be output to
	131	the system log. While this is useful for debugging, it's also
	132	a security threat - your keypresses include your passwords, of
	133	course.
	134
	135	If unsure, say N.
	136
	137	To compile this driver as a module, choose M here: the
	138	module will be called evbug.
	139
e17bb1de RP	140	config INPUT_APMPOWER
	141	tristate "Input Power Event -> APM Bridge" if EMBEDDED
	142	depends on INPUT && APM_EMULATION
	143	---help---
	144	Say Y here if you want suspend key events to trigger a user
	145	requested suspend through APM. This is useful on embedded
692105b8	146	systems where such behaviour is desired without userspace
e17bb1de RP	147	interaction. If unsure, say N.
	148
	149	To compile this driver as a module, choose M here: the
	150	module will be called apm-power.
	151
4ee36dc0 MA	152	config XEN_KBDDEV_FRONTEND
	153	tristate "Xen virtual keyboard and mouse support"
	154	depends on XEN_FBDEV_FRONTEND
	155	default y
	156	help
	157	This driver implements the front-end of the Xen virtual
	158	keyboard and mouse device driver. It communicates with a back-end
	159	in another domain.
	160
1da177e4 LT	161	comment "Input Device Drivers"
	162
	163	source "drivers/input/keyboard/Kconfig"
	164
	165	source "drivers/input/mouse/Kconfig"
	166
	167	source "drivers/input/joystick/Kconfig"
	168
4104d13f DT	169	source "drivers/input/tablet/Kconfig"
4104d13f DT	170
1da177e4 LT	171	source "drivers/input/touchscreen/Kconfig"
	172
	173	source "drivers/input/misc/Kconfig"
	174
	175	endif
	176
	177	menu "Hardware I/O ports"
	178
	179	source "drivers/input/serio/Kconfig"
	180
	181	source "drivers/input/gameport/Kconfig"
	182
	183	endmenu
	184
	185	endmenu
	186