2 # Input device configuration
5 menu "Input device support"
9 tristate "Generic input layer (needed for keyboard, mouse, ...)" if EXPERT
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
17 Say N here if you have a headless (no monitor, no keyboard) system.
19 More information is available: <file:Documentation/input/input.txt>
23 To compile this driver as a module, choose M here: the
24 module will be called input.
29 tristate "Export input device LEDs in sysfs"
33 Say Y here if you would like to export LEDs on input devices
34 as standard LED class devices in sysfs.
38 To compile this driver as a module, choose M here: the
39 module will be called input-leds.
41 config INPUT_FF_MEMLESS
42 tristate "Support for memoryless force-feedback devices"
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
51 To compile this driver as a module, choose M here: the
52 module will be called ff-memless.
55 tristate "Polled input device skeleton"
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.
64 To compile this driver as a module, choose M here: the
65 module will be called input-polldev.
67 config INPUT_SPARSEKMAP
68 tristate "Sparse keymap support library"
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.
77 To compile this driver as a module, choose M here: the
78 module will be called sparse-keymap.
80 config INPUT_MATRIXKMAP
81 tristate "Matrix keymap support library"
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.
90 To compile this driver as a module, choose M here: the
91 module will be called matrix-keymap.
93 comment "Userland interfaces"
96 tristate "Mouse interface"
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
107 To compile this driver as a module, choose M here: the
108 module will be called mousedev.
110 config INPUT_MOUSEDEV_PSAUX
111 bool "Provide legacy /dev/psaux device"
113 depends on INPUT_MOUSEDEV
115 Say Y here if you want your mouse also be accessible as char device
116 10:1 - /dev/psaux. The data available through /dev/psaux is exactly
117 the same as the data from /dev/input/mice.
122 config INPUT_MOUSEDEV_SCREEN_X
123 int "Horizontal screen resolution"
124 depends on INPUT_MOUSEDEV
127 If you're using a digitizer, or a graphic tablet, and want to use
128 it as a mouse then the mousedev driver needs to know the X window
129 screen resolution you are using to correctly scale the data. If
130 you're not using a digitizer, this value is ignored.
132 config INPUT_MOUSEDEV_SCREEN_Y
133 int "Vertical screen resolution"
134 depends on INPUT_MOUSEDEV
137 If you're using a digitizer, or a graphic tablet, and want to use
138 it as a mouse then the mousedev driver needs to know the X window
139 screen resolution you are using to correctly scale the data. If
140 you're not using a digitizer, this value is ignored.
143 tristate "Joystick interface"
145 Say Y here if you want your joystick or gamepad to be
146 accessible as char device 13:0+ - /dev/input/jsX device.
150 More information is available: <file:Documentation/input/joystick.txt>
152 To compile this driver as a module, choose M here: the
153 module will be called joydev.
156 tristate "Event interface"
158 Say Y here if you want your input device events be accessible
159 under char device 13:64+ - /dev/input/eventX in a generic way.
161 To compile this driver as a module, choose M here: the
162 module will be called evdev.
165 tristate "Event debugging"
167 Say Y here if you have a problem with the input subsystem and
168 want all events (keypresses, mouse movements), to be output to
169 the system log. While this is useful for debugging, it's also
170 a security threat - your keypresses include your passwords, of
175 To compile this driver as a module, choose M here: the
176 module will be called evbug.
178 config INPUT_APMPOWER
179 tristate "Input Power Event -> APM Bridge" if EXPERT
180 depends on INPUT && APM_EMULATION
182 Say Y here if you want suspend key events to trigger a user
183 requested suspend through APM. This is useful on embedded
184 systems where such behaviour is desired without userspace
185 interaction. If unsure, say N.
187 To compile this driver as a module, choose M here: the
188 module will be called apm-power.
190 config INPUT_KEYRESET
193 select INPUT_KEYCOMBO
195 Say Y here if you want to reboot when some keys are pressed;
197 config INPUT_KEYCOMBO
201 Say Y here if you want to take action when some keys are pressed;
203 comment "Input Device Drivers"
205 source "drivers/input/keyboard/Kconfig"
207 source "drivers/input/mouse/Kconfig"
209 source "drivers/input/joystick/Kconfig"
211 source "drivers/input/tablet/Kconfig"
213 source "drivers/input/touchscreen/Kconfig"
215 source "drivers/input/misc/Kconfig"
219 menu "Hardware I/O ports"
221 source "drivers/input/serio/Kconfig"
223 source "drivers/input/gameport/Kconfig"