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.
43 tristate "Polled input device skeleton"
45 Say Y here if you are using a driver for an input
46 device that periodically polls hardware state. This
47 option is only useful for out-of-tree drivers since
48 in-tree drivers select it automatically.
52 To compile this driver as a module, choose M here: the
53 module will be called input-polldev.
55 comment "Userland interfaces"
58 tristate "Mouse interface" if EMBEDDED
61 Say Y here if you want your mouse to be accessible as char devices
62 13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice as an
63 emulated IntelliMouse Explorer PS/2 mouse. That way, all user space
64 programs (including SVGAlib, GPM and X) will be able to use your
69 To compile this driver as a module, choose M here: the
70 module will be called mousedev.
72 config INPUT_MOUSEDEV_PSAUX
73 bool "Provide legacy /dev/psaux device"
75 depends on INPUT_MOUSEDEV
77 Say Y here if you want your mouse also be accessible as char device
78 10:1 - /dev/psaux. The data available through /dev/psaux is exactly
79 the same as the data from /dev/input/mice.
84 config INPUT_MOUSEDEV_SCREEN_X
85 int "Horizontal screen resolution"
86 depends on INPUT_MOUSEDEV
89 If you're using a digitizer, or a graphic tablet, and want to use
90 it as a mouse then the mousedev driver needs to know the X window
91 screen resolution you are using to correctly scale the data. If
92 you're not using a digitizer, this value is ignored.
94 config INPUT_MOUSEDEV_SCREEN_Y
95 int "Vertical screen resolution"
96 depends on INPUT_MOUSEDEV
99 If you're using a digitizer, or a graphic tablet, and want to use
100 it as a mouse then the mousedev driver needs to know the X window
101 screen resolution you are using to correctly scale the data. If
102 you're not using a digitizer, this value is ignored.
105 tristate "Joystick interface"
107 Say Y here if you want your joystick or gamepad to be
108 accessible as char device 13:0+ - /dev/input/jsX device.
112 More information is available: <file:Documentation/input/joystick.txt>
114 To compile this driver as a module, choose M here: the
115 module will be called joydev.
118 tristate "Event interface"
120 Say Y here if you want your input device events be accessible
121 under char device 13:64+ - /dev/input/eventX in a generic way.
123 To compile this driver as a module, choose M here: the
124 module will be called evdev.
127 tristate "Event debugging"
129 Say Y here if you have a problem with the input subsystem and
130 want all events (keypresses, mouse movements), to be output to
131 the system log. While this is useful for debugging, it's also
132 a security threat - your keypresses include your passwords, of
137 To compile this driver as a module, choose M here: the
138 module will be called evbug.
140 config INPUT_APMPOWER
141 tristate "Input Power Event -> APM Bridge" if EMBEDDED
142 depends on INPUT && APM_EMULATION
144 Say Y here if you want suspend key events to trigger a user
145 requested suspend through APM. This is useful on embedded
146 systems where such behviour is desired without userspace
147 interaction. If unsure, say N.
149 To compile this driver as a module, choose M here: the
150 module will be called apm-power.
152 comment "Input Device Drivers"
154 source "drivers/input/keyboard/Kconfig"
156 source "drivers/input/mouse/Kconfig"
158 source "drivers/input/joystick/Kconfig"
160 source "drivers/input/tablet/Kconfig"
162 source "drivers/input/touchscreen/Kconfig"
164 source "drivers/input/misc/Kconfig"
168 menu "Hardware I/O ports"
170 source "drivers/input/serio/Kconfig"
172 source "drivers/input/gameport/Kconfig"