2 # Input device configuration
5 menu "Input device support"
8 tristate "Generic input layer (needed for keyboard, mouse, ...)" if EMBEDDED
11 Say Y here if you have any input device (mouse, keyboard, tablet,
12 joystick, steering wheel ...) connected to your system and want
13 it to be available to applications. This includes standard PS/2
16 Say N here if you have a headless (no monitor, no keyboard) system.
18 More information is available: <file:Documentation/input/input.txt>
22 To compile this driver as a module, choose M here: the
23 module will be called input.
27 config INPUT_FF_MEMLESS
28 tristate "Support for memoryless force-feedback devices"
31 Say Y here if you have memoryless force-feedback input device
32 such as Logitech WingMan Force 3D, ThrustMaster FireStorm Dual
33 Power 2, or similar. You will also need to enable hardware-specific
38 To compile this driver as a module, choose M here: the
39 module will be called ff-memless.
42 tristate "Polled input device skeleton"
44 Say Y here if you are using a driver for an input
45 device that periodically polls hardware state. This
46 option is only useful for out-of-tree drivers since
47 in-tree drivers select it automatically.
51 To compile this driver as a module, choose M here: the
52 module will be called input-polldev.
54 comment "Userland interfaces"
57 tristate "Mouse interface" if EMBEDDED
60 Say Y here if you want your mouse to be accessible as char devices
61 13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice as an
62 emulated IntelliMouse Explorer PS/2 mouse. That way, all user space
63 programs (including SVGAlib, GPM and X) will be able to use your
68 To compile this driver as a module, choose M here: the
69 module will be called mousedev.
71 config INPUT_MOUSEDEV_PSAUX
72 bool "Provide legacy /dev/psaux device"
74 depends on INPUT_MOUSEDEV
76 Say Y here if you want your mouse also be accessible as char device
77 10:1 - /dev/psaux. The data available through /dev/psaux is exactly
78 the same as the data from /dev/input/mice.
83 config INPUT_MOUSEDEV_SCREEN_X
84 int "Horizontal screen resolution"
85 depends on INPUT_MOUSEDEV
88 If you're using a digitizer, or a graphic tablet, and want to use
89 it as a mouse then the mousedev driver needs to know the X window
90 screen resolution you are using to correctly scale the data. If
91 you're not using a digitizer, this value is ignored.
93 config INPUT_MOUSEDEV_SCREEN_Y
94 int "Vertical screen resolution"
95 depends on INPUT_MOUSEDEV
98 If you're using a digitizer, or a graphic tablet, and want to use
99 it as a mouse then the mousedev driver needs to know the X window
100 screen resolution you are using to correctly scale the data. If
101 you're not using a digitizer, this value is ignored.
104 tristate "Joystick interface"
106 Say Y here if you want your joystick or gamepad to be
107 accessible as char device 13:0+ - /dev/input/jsX device.
111 More information is available: <file:Documentation/input/joystick.txt>
113 To compile this driver as a module, choose M here: the
114 module will be called joydev.
117 tristate "Touchscreen interface"
119 Say Y here if you have an application that only can understand the
120 Compaq touchscreen protocol for absolute pointer data. This is
121 useful namely for embedded configurations.
125 To compile this driver as a module, choose M here: the
126 module will be called tsdev.
128 config INPUT_TSDEV_SCREEN_X
129 int "Horizontal screen resolution"
130 depends on INPUT_TSDEV
133 config INPUT_TSDEV_SCREEN_Y
134 int "Vertical screen resolution"
135 depends on INPUT_TSDEV
139 tristate "Event interface"
141 Say Y here if you want your input device events be accessible
142 under char device 13:64+ - /dev/input/eventX in a generic way.
144 To compile this driver as a module, choose M here: the
145 module will be called evdev.
148 tristate "Event debugging"
150 Say Y here if you have a problem with the input subsystem and
151 want all events (keypresses, mouse movements), to be output to
152 the system log. While this is useful for debugging, it's also
153 a security threat - your keypresses include your passwords, of
158 To compile this driver as a module, choose M here: the
159 module will be called evbug.
161 comment "Input Device Drivers"
163 source "drivers/input/keyboard/Kconfig"
165 source "drivers/input/mouse/Kconfig"
167 source "drivers/input/joystick/Kconfig"
169 source "drivers/input/tablet/Kconfig"
171 source "drivers/input/touchscreen/Kconfig"
173 source "drivers/input/misc/Kconfig"
177 menu "Hardware I/O ports"
179 source "drivers/input/serio/Kconfig"
181 source "drivers/input/gameport/Kconfig"