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.
41 comment "Userland interfaces"
44 tristate "Mouse interface" if EMBEDDED
47 Say Y here if you want your mouse to be accessible as char devices
48 13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice as an
49 emulated IntelliMouse Explorer PS/2 mouse. That way, all user space
50 programs (including SVGAlib, GPM and X) will be able to use your
55 To compile this driver as a module, choose M here: the
56 module will be called mousedev.
58 config INPUT_MOUSEDEV_PSAUX
59 bool "Provide legacy /dev/psaux device"
61 depends on INPUT_MOUSEDEV
63 Say Y here if you want your mouse also be accessible as char device
64 10:1 - /dev/psaux. The data available through /dev/psaux is exactly
65 the same as the data from /dev/input/mice.
70 config INPUT_MOUSEDEV_SCREEN_X
71 int "Horizontal screen resolution"
72 depends on INPUT_MOUSEDEV
75 If you're using a digitizer, or a graphic tablet, and want to use
76 it as a mouse then the mousedev driver needs to know the X window
77 screen resolution you are using to correctly scale the data. If
78 you're not using a digitizer, this value is ignored.
80 config INPUT_MOUSEDEV_SCREEN_Y
81 int "Vertical screen resolution"
82 depends on INPUT_MOUSEDEV
85 If you're using a digitizer, or a graphic tablet, and want to use
86 it as a mouse then the mousedev driver needs to know the X window
87 screen resolution you are using to correctly scale the data. If
88 you're not using a digitizer, this value is ignored.
91 tristate "Joystick interface"
93 Say Y here if you want your joystick or gamepad to be
94 accessible as char device 13:0+ - /dev/input/jsX device.
98 More information is available: <file:Documentation/input/joystick.txt>
100 To compile this driver as a module, choose M here: the
101 module will be called joydev.
104 tristate "Touchscreen interface"
106 Say Y here if you have an application that only can understand the
107 Compaq touchscreen protocol for absolute pointer data. This is
108 useful namely for embedded configurations.
112 To compile this driver as a module, choose M here: the
113 module will be called tsdev.
115 config INPUT_TSDEV_SCREEN_X
116 int "Horizontal screen resolution"
117 depends on INPUT_TSDEV
120 config INPUT_TSDEV_SCREEN_Y
121 int "Vertical screen resolution"
122 depends on INPUT_TSDEV
126 tristate "Event interface"
128 Say Y here if you want your input device events be accessible
129 under char device 13:64+ - /dev/input/eventX in a generic way.
131 To compile this driver as a module, choose M here: the
132 module will be called evdev.
135 tristate "Event debugging"
137 Say Y here if you have a problem with the input subsystem and
138 want all events (keypresses, mouse movements), to be output to
139 the system log. While this is useful for debugging, it's also
140 a security threat - your keypresses include your passwords, of
145 To compile this driver as a module, choose M here: the
146 module will be called evbug.
148 comment "Input Device Drivers"
150 source "drivers/input/keyboard/Kconfig"
152 source "drivers/input/mouse/Kconfig"
154 source "drivers/input/joystick/Kconfig"
156 source "drivers/input/touchscreen/Kconfig"
158 source "drivers/input/misc/Kconfig"
162 menu "Hardware I/O ports"
164 source "drivers/input/serio/Kconfig"
166 source "drivers/input/gameport/Kconfig"