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" if EMBEDDED
46 depends on INPUT_MOUSEDEV
48 config INPUT_MOUSEDEV_SCREEN_X
49 int "Horizontal screen resolution"
50 depends on INPUT_MOUSEDEV
53 If you're using a digitizer, or a graphic tablet, and want to use
54 it as a mouse then the mousedev driver needs to know the X window
55 screen resolution you are using to correctly scale the data. If
56 you're not using a digitizer, this value is ignored.
58 config INPUT_MOUSEDEV_SCREEN_Y
59 int "Vertical screen resolution"
60 depends on INPUT_MOUSEDEV
63 If you're using a digitizer, or a graphic tablet, and want to use
64 it as a mouse then the mousedev driver needs to know the X window
65 screen resolution you are using to correctly scale the data. If
66 you're not using a digitizer, this value is ignored.
69 tristate "Joystick interface"
72 Say Y here if you want your joystick or gamepad to be
73 accessible as char device 13:0+ - /dev/input/jsX device.
77 More information is available: <file:Documentation/input/joystick.txt>
79 To compile this driver as a module, choose M here: the
80 module will be called joydev.
83 tristate "Touchscreen interface"
86 Say Y here if you have an application that only can understand the
87 Compaq touchscreen protocol for absolute pointer data. This is
88 useful namely for embedded configurations.
92 To compile this driver as a module, choose M here: the
93 module will be called tsdev.
95 config INPUT_TSDEV_SCREEN_X
96 int "Horizontal screen resolution"
97 depends on INPUT_TSDEV
100 config INPUT_TSDEV_SCREEN_Y
101 int "Vertical screen resolution"
102 depends on INPUT_TSDEV
106 tristate "Event interface"
109 Say Y here if you want your input device events be accessible
110 under char device 13:64+ - /dev/input/eventX in a generic way.
112 To compile this driver as a module, choose M here: the
113 module will be called evdev.
116 tristate "Event debugging"
119 Say Y here if you have a problem with the input subsystem and
120 want all events (keypresses, mouse movements), to be output to
121 the system log. While this is useful for debugging, it's also
122 a security threat - your keypresses include your passwords, of
127 To compile this driver as a module, choose M here: the
128 module will be called evbug.
130 comment "Input I/O drivers"
132 source "drivers/input/gameport/Kconfig"
134 source "drivers/input/serio/Kconfig"
136 comment "Input Device Drivers"
138 source "drivers/input/keyboard/Kconfig"
140 source "drivers/input/mouse/Kconfig"
142 source "drivers/input/joystick/Kconfig"
144 source "drivers/input/touchscreen/Kconfig"
146 source "drivers/input/misc/Kconfig"