#
# Input device configuration
#
menu "Input device support"
depends on ![31mCONFIG_UML[0m
config [31mCONFIG_INPUT[0m
tristate "Generic input layer (needed for keyboard, mouse, ...)" if [31mCONFIG_EXPERT[0m
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 [31mCONFIG_M[0m here: the
module will be called input.
if [31mCONFIG_INPUT[0m
config [31mCONFIG_INPUT_LEDS[0m
tristate "Export input device LEDs in sysfs"
depends on [31mCONFIG_LEDS_CLASS[0m
default [31mCONFIG_INPUT[0m
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 [31mCONFIG_M[0m here: the
module will be called input-leds.
config [31mCONFIG_INPUT_FF_MEMLESS[0m
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 [31mCONFIG_M[0m here: the
module will be called ff-memless.
config [31mCONFIG_INPUT_POLLDEV[0m
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 [31mCONFIG_M[0m here: the
module will be called input-polldev.
config [31mCONFIG_INPUT_SPARSEKMAP[0m
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 [31mCONFIG_M[0m here: the
module will be called sparse-keymap.
config [31mCONFIG_INPUT_MATRIXKMAP[0m
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 [31mCONFIG_M[0m here: the
module will be called matrix-keymap.
comment "Userland interfaces"
config [31mCONFIG_INPUT_MOUSEDEV[0m
tristate "Mouse interface"
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 [31mCONFIG_M[0m here: the
module will be called mousedev.
config [31mCONFIG_INPUT_MOUSEDEV_PSAUX[0m
bool "Provide legacy /dev/psaux device"
default y
depends on [31mCONFIG_INPUT_MOUSEDEV[0m
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 [31mCONFIG_INPUT_MOUSEDEV_SCREEN_X[0m
int "Horizontal screen resolution"
depends on [31mCONFIG_INPUT_MOUSEDEV[0m
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 [31mCONFIG_INPUT_MOUSEDEV_SCREEN_Y[0m
int "Vertical screen resolution"
depends on [31mCONFIG_INPUT_MOUSEDEV[0m
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 [31mCONFIG_INPUT_JOYDEV[0m
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 [31mCONFIG_M[0m here: the
module will be called joydev.
config [31mCONFIG_INPUT_EVDEV[0m
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 [31mCONFIG_M[0m here: the
module will be called evdev.
config [31mCONFIG_INPUT_EVBUG[0m
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 [31mCONFIG_M[0m here: the
module will be called evbug.
config [31mCONFIG_INPUT_APMPOWER[0m
tristate "Input Power Event -> APM Bridge" if [31mCONFIG_EXPERT[0m
depends on [31mCONFIG_INPUT[0m && [31mCONFIG_APM_EMULATION[0m
help
Say Y here if you want suspend key events to trigger a user
requested suspend through [31mCONFIG_APM[0m. 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 [31mCONFIG_M[0m 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