[mirror_ubuntu-focal-kernel.git] / drivers / input / Kconfig

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