2 # Input device configuration
5 menu "Input device support"
8 tristate "Input devices (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.
25 comment "Userland interfaces"
28 tristate "Mouse interface" if EMBEDDED
32 Say Y here if you want your mouse to be accessible as char devices
33 13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice as an
34 emulated IntelliMouse Explorer PS/2 mouse. That way, all user space
35 programs (includung SVGAlib, GPM and X) will be able to use your
40 To compile this driver as a module, choose M here: the
41 module will be called mousedev.
43 config INPUT_MOUSEDEV_PSAUX
44 bool "Provide legacy /dev/psaux device"
46 depends on INPUT_MOUSEDEV
48 Say Y here if you want your mouse also be accessible as char device
49 10:1 - /dev/psaux. The data available through /dev/psaux is exactly
50 the same as the data from /dev/input/mice.
55 config INPUT_MOUSEDEV_SCREEN_X
56 int "Horizontal screen resolution"
57 depends on INPUT_MOUSEDEV
60 If you're using a digitizer, or a graphic tablet, and want to use
61 it as a mouse then the mousedev driver needs to know the X window
62 screen resolution you are using to correctly scale the data. If
63 you're not using a digitizer, this value is ignored.
65 config INPUT_MOUSEDEV_SCREEN_Y
66 int "Vertical screen resolution"
67 depends on INPUT_MOUSEDEV
70 If you're using a digitizer, or a graphic tablet, and want to use
71 it as a mouse then the mousedev driver needs to know the X window
72 screen resolution you are using to correctly scale the data. If
73 you're not using a digitizer, this value is ignored.
76 tristate "Joystick interface"
79 Say Y here if you want your joystick or gamepad to be
80 accessible as char device 13:0+ - /dev/input/jsX device.
84 More information is available: <file:Documentation/input/joystick.txt>
86 To compile this driver as a module, choose M here: the
87 module will be called joydev.
90 tristate "Touchscreen interface"
93 Say Y here if you have an application that only can understand the
94 Compaq touchscreen protocol for absolute pointer data. This is
95 useful namely for embedded configurations.
99 To compile this driver as a module, choose M here: the
100 module will be called tsdev.
102 config INPUT_TSDEV_SCREEN_X
103 int "Horizontal screen resolution"
104 depends on INPUT_TSDEV
107 config INPUT_TSDEV_SCREEN_Y
108 int "Vertical screen resolution"
109 depends on INPUT_TSDEV
113 tristate "Event interface"
116 Say Y here if you want your input device events be accessible
117 under char device 13:64+ - /dev/input/eventX in a generic way.
119 To compile this driver as a module, choose M here: the
120 module will be called evdev.
123 tristate "Event debugging"
126 Say Y here if you have a problem with the input subsystem and
127 want all events (keypresses, mouse movements), to be output to
128 the system log. While this is useful for debugging, it's also
129 a security threat - your keypresses include your passwords, of
134 To compile this driver as a module, choose M here: the
135 module will be called evbug.
137 comment "Input I/O drivers"
139 source "drivers/input/gameport/Kconfig"
141 source "drivers/input/serio/Kconfig"
143 comment "Input Device Drivers"
145 source "drivers/input/keyboard/Kconfig"
147 source "drivers/input/mouse/Kconfig"
149 source "drivers/input/joystick/Kconfig"
151 source "drivers/input/touchscreen/Kconfig"
153 source "drivers/input/misc/Kconfig"