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

#
# Input device configuration
#

menu "Input device support"
	depends on !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.rst>

	  If unsure, say Y.

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

if INPUT

config INPUT_LEDS
	tristate "Export input device LEDs in sysfs"
	depends on LEDS_CLASS
	default INPUT
	help
	  Say Y here if you would like to export LEDs on input devices
	  as standard LED class devices in sysfs.

	  If unsure, say Y.

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

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.

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

comment "Userland interfaces"

config INPUT_MOUSEDEV
	tristate "Mouse interface"
	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"
	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/joydev/joystick.rst>

	  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"

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