Blame view

kernel/linux-imx6_3.14.28/drivers/input/Kconfig 5.63 KB
6b13f685e   김민수   BSP 최초 추가
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
  #
  # Input device configuration
  #
  
  menu "Input device support"
  	depends on !UML
  
  config INPUT
  	tristate "Generic input layer (needed for keyboard, mouse, ...)" if EXPERT
  	default y
  	help
  	  Say Y here if you have any input device (mouse, keyboard, tablet,
  	  joystick, steering wheel ...) connected to your system and want
  	  it to be available to applications. This includes standard PS/2
  	  keyboard and mouse.
  
  	  Say N here if you have a headless (no monitor, no keyboard) system.
  
  	  More information is available: <file:Documentation/input/input.txt>
  
  	  If unsure, say Y.
  
  	  To compile this driver as a module, choose M here: the
  	  module will be called input.
  
  if INPUT
  
  config INPUT_FF_MEMLESS
  	tristate "Support for memoryless force-feedback devices"
  	help
  	  Say Y here if you have memoryless force-feedback input device
  	  such as Logitech WingMan Force 3D, ThrustMaster FireStorm Dual
  	  Power 2, or similar. You will also need to enable hardware-specific
  	  driver.
  
  	  If unsure, say N.
  
  	  To compile this driver as a module, choose M here: the
  	  module will be called ff-memless.
  
  config INPUT_POLLDEV
  	tristate "Polled input device skeleton"
  	help
  	  Say Y here if you are using a driver for an input
  	  device that periodically polls hardware state. This
  	  option is only useful for out-of-tree drivers since
  	  in-tree drivers select it automatically.
  
  	  If unsure, say N.
  
  	  To compile this driver as a module, choose M here: the
  	  module will be called input-polldev.
  
  config INPUT_SPARSEKMAP
  	tristate "Sparse keymap support library"
  	help
  	  Say Y here if you are using a driver for an input
  	  device that uses sparse keymap. This option is only
  	  useful for out-of-tree drivers since in-tree drivers
  	  select it automatically.
  
  	  If unsure, say N.
  
  	  To compile this driver as a module, choose M here: the
  	  module will be called sparse-keymap.
  
  config INPUT_MATRIXKMAP
  	tristate "Matrix keymap support library"
  	help
  	  Say Y here if you are using a driver for an input
  	  device that uses matrix keymap. This option is only
  	  useful for out-of-tree drivers since in-tree drivers
  	  select it automatically.
  
  	  If unsure, say N.
  
  	  To compile this driver as a module, choose M here: the
  	  module will be called matrix-keymap.
  
  comment "Userland interfaces"
  
  config INPUT_MOUSEDEV
  	tristate "Mouse interface"
  	default y
  	help
  	  Say Y here if you want your mouse to be accessible as char devices
  	  13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice as an
  	  emulated IntelliMouse Explorer PS/2 mouse. That way, all user space
  	  programs (including SVGAlib, GPM and X) will be able to use your
  	  mouse.
  
  	  If unsure, say Y.
  
  	  To compile this driver as a module, choose M here: the
  	  module will be called mousedev.
  
  config INPUT_MOUSEDEV_PSAUX
  	bool "Provide legacy /dev/psaux device"
  	default y
  	depends on INPUT_MOUSEDEV
  	help
  	  Say Y here if you want your mouse also be accessible as char device
  	  10:1 - /dev/psaux. The data available through /dev/psaux is exactly
  	  the same as the data from /dev/input/mice.
  
  	  If unsure, say Y.
  
  
  config INPUT_MOUSEDEV_SCREEN_X
  	int "Horizontal screen resolution"
  	depends on INPUT_MOUSEDEV
  	default "1024"
  	help
  	  If you're using a digitizer, or a graphic tablet, and want to use
  	  it as a mouse then the mousedev driver needs to know the X window
  	  screen resolution you are using to correctly scale the data. If
  	  you're not using a digitizer, this value is ignored.
  
  config INPUT_MOUSEDEV_SCREEN_Y
  	int "Vertical screen resolution"
  	depends on INPUT_MOUSEDEV
  	default "768"
  	help
  	  If you're using a digitizer, or a graphic tablet, and want to use
  	  it as a mouse then the mousedev driver needs to know the X window
  	  screen resolution you are using to correctly scale the data. If
  	  you're not using a digitizer, this value is ignored.
  
  config INPUT_JOYDEV
  	tristate "Joystick interface"
  	help
  	  Say Y here if you want your joystick or gamepad to be
  	  accessible as char device 13:0+ - /dev/input/jsX device.
  
  	  If unsure, say Y.
  
  	  More information is available: <file:Documentation/input/joystick.txt>
  
  	  To compile this driver as a module, choose M here: the
  	  module will be called joydev.
  
  config INPUT_EVDEV
  	tristate "Event interface"
  	help
  	  Say Y here if you want your input device events be accessible
  	  under char device 13:64+ - /dev/input/eventX in a generic way.
  
  	  To compile this driver as a module, choose M here: the
  	  module will be called evdev.
  
  config INPUT_EVBUG
  	tristate "Event debugging"
  	help
  	  Say Y here if you have a problem with the input subsystem and
  	  want all events (keypresses, mouse movements), to be output to
  	  the system log. While this is useful for debugging, it's also
  	  a security threat - your keypresses include your passwords, of
  	  course.
  
  	  If unsure, say N.
  
  	  To compile this driver as a module, choose M here: the
  	  module will be called evbug.
  
  config INPUT_APMPOWER
  	tristate "Input Power Event -> APM Bridge" if EXPERT
  	depends on INPUT && APM_EMULATION
  	help
  	  Say Y here if you want suspend key events to trigger a user
  	  requested suspend through APM. This is useful on embedded
  	  systems where such behaviour is desired without userspace
  	  interaction. If unsure, say N.
  
  	  To compile this driver as a module, choose M here: the
  	  module will be called apm-power.
  
  comment "Input Device Drivers"
  
  source "drivers/input/keyboard/Kconfig"
  
  source "drivers/input/mouse/Kconfig"
  
  source "drivers/input/joystick/Kconfig"
  
  source "drivers/input/tablet/Kconfig"
  
  source "drivers/input/touchscreen/Kconfig"
  
  source "drivers/input/misc/Kconfig"
  
  endif
  
  menu "Hardware I/O ports"
  
  source "drivers/input/serio/Kconfig"
  
  source "drivers/input/gameport/Kconfig"
  
  endmenu
  
  endmenu