[deliverable/linux.git] / drivers / input / Kconfig

#
# Input device configuration
#

menu "Input device support"
	depends on !S390 && !UML

config INPUT
	tristate "Generic input layer (needed for keyboard, mouse, ...)" if EXPERT
	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_OF_MATRIX_KEYMAP
	depends on USE_OF
	bool

config INPUT_FF_MEMLESS
	tristate "Support for memoryless force-feedback devices"
	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.

config INPUT_SPARSEKMAP
	tristate "Sparse keymap support library"
	help
	  Say Y here if you are using a driver for an input
	  device that uses sparse keymap. 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 sparse-keymap.

comment "Userland interfaces"

config INPUT_MOUSEDEV
	tristate "Mouse interface" if EXPERT
	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 EXPERT
	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.

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