blob: 96232313b1b97fc277aeb4c67ebff59d205eb6aa [file] [log] [blame]
Linus Torvalds1da177e2005-04-16 15:20:36 -07001#
2# Input device configuration
3#
4
5menu "Input device support"
6
7config INPUT
8 tristate "Generic input layer (needed for keyboard, mouse, ...)" if EMBEDDED
9 default y
10 ---help---
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
14 keyboard and mouse.
15
16 Say N here if you have a headless (no monitor, no keyboard) system.
17
18 More information is available: <file:Documentation/input/input.txt>
19
20 If unsure, say Y.
21
22 To compile this driver as a module, choose M here: the
23 module will be called input.
24
25if INPUT
26
Anssi Hannula7d928a22006-07-19 01:40:30 -040027config INPUT_FF_MEMLESS
28 tristate "Support for memoryless force-feedback devices"
29 default n
30 ---help---
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
34 driver.
35
36 If unsure, say N.
37
38 To compile this driver as a module, choose M here: the
39 module will be called ff-memless.
40
Linus Torvalds1da177e2005-04-16 15:20:36 -070041comment "Userland interfaces"
42
43config INPUT_MOUSEDEV
44 tristate "Mouse interface" if EMBEDDED
45 default y
46 ---help---
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
51 mouse.
52
53 If unsure, say Y.
54
55 To compile this driver as a module, choose M here: the
56 module will be called mousedev.
57
58config INPUT_MOUSEDEV_PSAUX
59 bool "Provide legacy /dev/psaux device"
60 default y
61 depends on INPUT_MOUSEDEV
62 ---help---
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.
66
67 If unsure, say Y.
68
69
70config INPUT_MOUSEDEV_SCREEN_X
71 int "Horizontal screen resolution"
72 depends on INPUT_MOUSEDEV
73 default "1024"
74 help
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.
79
80config INPUT_MOUSEDEV_SCREEN_Y
81 int "Vertical screen resolution"
82 depends on INPUT_MOUSEDEV
83 default "768"
84 help
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.
89
90config INPUT_JOYDEV
91 tristate "Joystick interface"
92 ---help---
93 Say Y here if you want your joystick or gamepad to be
94 accessible as char device 13:0+ - /dev/input/jsX device.
95
96 If unsure, say Y.
97
98 More information is available: <file:Documentation/input/joystick.txt>
99
100 To compile this driver as a module, choose M here: the
101 module will be called joydev.
102
103config INPUT_TSDEV
104 tristate "Touchscreen interface"
105 ---help---
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.
109
110 If unsure, say N.
111
112 To compile this driver as a module, choose M here: the
113 module will be called tsdev.
114
115config INPUT_TSDEV_SCREEN_X
116 int "Horizontal screen resolution"
117 depends on INPUT_TSDEV
118 default "240"
119
120config INPUT_TSDEV_SCREEN_Y
121 int "Vertical screen resolution"
122 depends on INPUT_TSDEV
123 default "320"
124
125config INPUT_EVDEV
126 tristate "Event interface"
127 help
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.
130
131 To compile this driver as a module, choose M here: the
132 module will be called evdev.
133
134config INPUT_EVBUG
135 tristate "Event debugging"
136 ---help---
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
141 course.
142
143 If unsure, say N.
144
145 To compile this driver as a module, choose M here: the
146 module will be called evbug.
147
148comment "Input Device Drivers"
149
150source "drivers/input/keyboard/Kconfig"
151
152source "drivers/input/mouse/Kconfig"
153
154source "drivers/input/joystick/Kconfig"
155
156source "drivers/input/touchscreen/Kconfig"
157
158source "drivers/input/misc/Kconfig"
159
160endif
161
162menu "Hardware I/O ports"
163
164source "drivers/input/serio/Kconfig"
165
166source "drivers/input/gameport/Kconfig"
167
168endmenu
169
170endmenu
171