2 # Input device configuration
5 menu "Input device support"
9 tristate "Generic input layer (needed for keyboard, mouse, ...)" if EMBEDDED
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.
28 config INPUT_FF_MEMLESS
29 tristate "Support for memoryless force-feedback devices"
32 Say Y here if you have memoryless force-feedback input device
33 such as Logitech WingMan Force 3D, ThrustMaster FireStorm Dual
34 Power 2, or similar. You will also need to enable hardware-specific
39 To compile this driver as a module, choose M here: the
40 module will be called ff-memless.
42 comment "Userland interfaces"
45 tristate "Mouse interface" if EMBEDDED
48 Say Y here if you want your mouse to be accessible as char devices
49 13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice as an
50 emulated IntelliMouse Explorer PS/2 mouse. That way, all user space
51 programs (including SVGAlib, GPM and X) will be able to use your
56 To compile this driver as a module, choose M here: the
57 module will be called mousedev.
59 config INPUT_MOUSEDEV_PSAUX
60 bool "Provide legacy /dev/psaux device"
62 depends on INPUT_MOUSEDEV
64 Say Y here if you want your mouse also be accessible as char device
65 10:1 - /dev/psaux. The data available through /dev/psaux is exactly
66 the same as the data from /dev/input/mice.
71 config INPUT_MOUSEDEV_SCREEN_X
72 int "Horizontal screen resolution"
73 depends on INPUT_MOUSEDEV
76 If you're using a digitizer, or a graphic tablet, and want to use
77 it as a mouse then the mousedev driver needs to know the X window
78 screen resolution you are using to correctly scale the data. If
79 you're not using a digitizer, this value is ignored.
81 config INPUT_MOUSEDEV_SCREEN_Y
82 int "Vertical screen resolution"
83 depends on INPUT_MOUSEDEV
86 If you're using a digitizer, or a graphic tablet, and want to use
87 it as a mouse then the mousedev driver needs to know the X window
88 screen resolution you are using to correctly scale the data. If
89 you're not using a digitizer, this value is ignored.
92 tristate "Joystick interface"
94 Say Y here if you want your joystick or gamepad to be
95 accessible as char device 13:0+ - /dev/input/jsX device.
99 More information is available: <file:Documentation/input/joystick.txt>
101 To compile this driver as a module, choose M here: the
102 module will be called joydev.
105 tristate "Touchscreen interface"
107 Say Y here if you have an application that only can understand the
108 Compaq touchscreen protocol for absolute pointer data. This is
109 useful namely for embedded configurations.
113 To compile this driver as a module, choose M here: the
114 module will be called tsdev.
116 config INPUT_TSDEV_SCREEN_X
117 int "Horizontal screen resolution"
118 depends on INPUT_TSDEV
121 config INPUT_TSDEV_SCREEN_Y
122 int "Vertical screen resolution"
123 depends on INPUT_TSDEV
127 tristate "Event interface"
129 Say Y here if you want your input device events be accessible
130 under char device 13:64+ - /dev/input/eventX in a generic way.
132 To compile this driver as a module, choose M here: the
133 module will be called evdev.
136 tristate "Event debugging"
138 Say Y here if you have a problem with the input subsystem and
139 want all events (keypresses, mouse movements), to be output to
140 the system log. While this is useful for debugging, it's also
141 a security threat - your keypresses include your passwords, of
146 To compile this driver as a module, choose M here: the
147 module will be called evbug.
149 comment "Input Device Drivers"
151 source "drivers/input/keyboard/Kconfig"
153 source "drivers/input/mouse/Kconfig"
155 source "drivers/input/joystick/Kconfig"
157 source "drivers/input/tablet/Kconfig"
159 source "drivers/input/touchscreen/Kconfig"
161 source "drivers/input/misc/Kconfig"
165 menu "Hardware I/O ports"
167 source "drivers/input/serio/Kconfig"
169 source "drivers/input/gameport/Kconfig"