Kconfig 13.3 KB
Newer Older
L
Linus Torvalds 已提交
1 2 3 4 5 6 7 8 9 10 11 12 13 14
#
# Input misc drivers configuration
#
menuconfig INPUT_MISC
	bool "Miscellaneous devices"
	help
	  Say Y here, and a list of miscellaneous input drivers will be displayed.
	  Everything that didn't fit into the other categories is here. This option
	  doesn't affect the kernel.

	  If unsure, say Y.

if INPUT_MISC

15 16 17 18 19 20 21 22 23 24
config INPUT_88PM860X_ONKEY
	tristate "88PM860x ONKEY support"
	depends on MFD_88PM860X
	help
	  Support the ONKEY of Marvell 88PM860x PMICs as an input device
	  reporting power button status.

	  To compile this driver as a module, choose M here: the module
	  will be called 88pm860x_onkey.

25 26 27 28 29 30 31 32 33 34
config INPUT_AB8500_PONKEY
	tristate "AB8500 Pon (PowerOn) Key"
	depends on AB8500_CORE
	help
	  Say Y here to use the PowerOn Key for ST-Ericsson's AB8500
	  Mix-Sig PMIC.

	  To compile this driver as a module, choose M here: the module
	  will be called ab8500-ponkey.

35 36 37
config INPUT_AD714X
	tristate "Analog Devices AD714x Capacitance Touch Sensor"
	help
38
	  Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
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

	  You should select a bus connection too.

	  To compile this driver as a module, choose M here: the
	  module will be called ad714x.

config INPUT_AD714X_I2C
	tristate "support I2C bus connection"
	depends on INPUT_AD714X && I2C
	default y
	help
	  Say Y here if you have AD7142/AD7147 hooked to an I2C bus.

	  To compile this driver as a module, choose M here: the
	  module will be called ad714x-i2c.

config INPUT_AD714X_SPI
	tristate "support SPI bus connection"
	depends on INPUT_AD714X && SPI
	default y
	help
	  Say Y here if you have AD7142/AD7147 hooked to a SPI bus.

	  To compile this driver as a module, choose M here: the
	  module will be called ad714x-spi.

L
Linus Torvalds 已提交
65 66
config INPUT_PCSPKR
	tristate "PC Speaker support"
S
Stas Sergeev 已提交
67
	depends on PCSPKR_PLATFORM
L
Linus Torvalds 已提交
68 69 70 71 72 73 74 75 76 77 78
	help
	  Say Y here if you want the standard PC Speaker to be used for
	  bells and whistles.

	  If unsure, say Y.

	  To compile this driver as a module, choose M here: the
	  module will be called pcspkr.

config INPUT_SPARCSPKR
	tristate "SPARC Speaker support"
79
	depends on PCI && SPARC64
L
Linus Torvalds 已提交
80 81 82 83 84 85 86 87 88 89 90 91 92
	help
	  Say Y here if you want the standard Speaker on Sparc PCI systems
	  to be used for bells and whistles.

	  If unsure, say Y.

	  To compile this driver as a module, choose M here: the
	  module will be called sparcspkr.

config INPUT_M68K_BEEP
	tristate "M68k Beeper support"
	depends on M68K

93 94 95 96 97 98 99 100 101 102
config INPUT_MAX8925_ONKEY
	tristate "MAX8925 ONKEY support"
	depends on MFD_MAX8925
	help
	  Support the ONKEY of MAX8925 PMICs as an input device
	  reporting power button status.

	  To compile this driver as a module, choose M here: the module
	  will be called max8925_onkey.

103 104
config INPUT_APANEL
	tristate "Fujitsu Lifebook Application Panel buttons"
105
	depends on X86 && I2C && LEDS_CLASS
106 107 108 109 110
	select INPUT_POLLDEV
	select CHECK_SIGNATURE
	help
	 Say Y here for support of the Application Panel buttons, used on
	 Fujitsu Lifebook. These are attached to the mainboard through
111 112
	 an SMBus interface managed by the I2C Intel ICH (i801) driver,
	 which you should also build for this kernel.
113 114 115 116

	 To compile this driver as a module, choose M here: the module will
	 be called apanel.

117 118 119 120 121 122 123 124 125 126 127 128
config INPUT_IXP4XX_BEEPER
	tristate "IXP4XX Beeper support"
	depends on ARCH_IXP4XX
	help
	  If you say yes here, you can connect a beeper to the
	  ixp4xx gpio pins. This is used by the LinkSys NSLU2.

	  If unsure, say Y.

	  To compile this driver as a module, choose M here: the
	  module will be called ixp4xx-beeper.

129 130 131
config INPUT_COBALT_BTNS
	tristate "Cobalt button interface"
	depends on MIPS_COBALT
132
	select INPUT_POLLDEV
133 134 135 136 137 138
	help
	  Say Y here if you want to support MIPS Cobalt button interface.

	  To compile this driver as a module, choose M here: the
	  module will be called cobalt_btns.

D
Dmitry Torokhov 已提交
139 140
config INPUT_WISTRON_BTNS
	tristate "x86 Wistron laptop button interface"
141
	depends on X86 && !X86_64
142
	select INPUT_POLLDEV
143
	select INPUT_SPARSEKMAP
E
Eric Piel 已提交
144 145
	select NEW_LEDS
	select LEDS_CLASS
146
	select CHECK_SIGNATURE
D
Dmitry Torokhov 已提交
147
	help
M
Matt LaPlante 已提交
148
	  Say Y here for support of Wistron laptop button interfaces, used on
E
Eric Piel 已提交
149
	  laptops of various brands, including Acer and Fujitsu-Siemens. If
M
Matt LaPlante 已提交
150
	  available, mail and wifi LEDs will be controllable via /sys/class/leds.
D
Dmitry Torokhov 已提交
151 152 153 154

	  To compile this driver as a module, choose M here: the module will
	  be called wistron_btns.

J
Jaya Kumar 已提交
155 156 157 158 159 160 161 162 163 164
config INPUT_ATLAS_BTNS
	tristate "x86 Atlas button interface"
	depends on X86 && ACPI
	help
	  Say Y here for support of Atlas wallmount touchscreen buttons.
	  The events will show up as scancodes F1 through F9 via evdev.

	  To compile this driver as a module, choose M here: the module will
	  be called atlas_btns.

165 166
config INPUT_ATI_REMOTE
	tristate "ATI / X10 USB RF remote control"
167
	depends on USB_ARCH_HAS_HCD
168
	select USB
169
	help
170 171 172 173 174 175 176 177 178 179 180 181 182
	  Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
	  These are RF remotes with USB receivers.
	  The ATI remote comes with many of ATI's All-In-Wonder video cards.
	  The X10 "Lola" remote is available at:
	     <http://www.x10.com/products/lola_sg1.htm>
	  This driver provides mouse pointer, left and right mouse buttons,
	  and maps all the other remote buttons to keypress events.

	  To compile this driver as a module, choose M here: the module will be
	  called ati_remote.

config INPUT_ATI_REMOTE2
	tristate "ATI / Philips USB RF remote control"
183
	depends on USB_ARCH_HAS_HCD
184 185 186 187 188 189 190 191 192 193 194 195 196 197 198
	select USB
	help
	  Say Y here if you want to use an ATI or Philips USB RF remote control.
	  These are RF remotes with USB receivers.
	  ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
	  and is also available as a separate product.
	  This driver provides mouse pointer, left and right mouse buttons,
	  and maps all the other remote buttons to keypress events.

	  To compile this driver as a module, choose M here: the module will be
	  called ati_remote2.

config INPUT_KEYSPAN_REMOTE
	tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
	depends on EXPERIMENTAL
199
	depends on USB_ARCH_HAS_HCD
200 201 202 203 204 205 206 207
	select USB
	help
	  Say Y here if you want to use a Keyspan DMR USB remote control.
	  Currently only the UIA-11 type of receiver has been tested.  The tag
	  on the receiver that connects to the USB port should have a P/N that
	  will tell you what type of DMR you have.  The UIA-10 type is not
	  supported at this time.  This driver maps all buttons to keypress
	  events.
208

209 210 211 212 213
	  To compile this driver as a module, choose M here: the module will
	  be called keyspan_remote.

config INPUT_POWERMATE
	tristate "Griffin PowerMate and Contour Jog support"
214
	depends on USB_ARCH_HAS_HCD
215 216 217 218 219 220 221 222 223
	select USB
	help
	  Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
	  These are aluminum dials which can measure clockwise and anticlockwise
	  rotation.  The dial also acts as a pushbutton.  The base contains an LED
	  which can be instructed to pulse or to switch to a particular intensity.

	  You can download userspace tools from
	  <http://sowerbutts.com/powermate/>.
224 225

	  To compile this driver as a module, choose M here: the
226 227 228 229
	  module will be called powermate.

config INPUT_YEALINK
	tristate "Yealink usb-p1k voip phone"
230
	depends on EXPERIMENTAL
231
	depends on USB_ARCH_HAS_HCD
232 233 234 235 236 237 238 239 240 241 242
	select USB
	help
	  Say Y here if you want to enable keyboard and LCD functions of the
	  Yealink usb-p1k usb phones. The audio part is enabled by the generic
	  usb sound driver, so you might want to enable that as well.

	  For information about how to use these additional functions, see
	  <file:Documentation/input/yealink.txt>.

	  To compile this driver as a module, choose M here: the module will be
	  called yealink.
243

244 245 246 247 248 249 250 251 252 253 254 255 256
config INPUT_CM109
	tristate "C-Media CM109 USB I/O Controller"
	depends on EXPERIMENTAL
	depends on USB_ARCH_HAS_HCD
	select USB
	help
	  Say Y here if you want to enable keyboard and buzzer functions of the
	  C-Media CM109 usb phones. The audio part is enabled by the generic
	  usb sound driver, so you might want to enable that as well.

	  To compile this driver as a module, choose M here: the module will be
	  called cm109.

257 258 259 260 261 262 263 264 265 266
config INPUT_TWL4030_PWRBUTTON
	tristate "TWL4030 Power button Driver"
	depends on TWL4030_CORE
	help
	  Say Y here if you want to enable power key reporting via the
	  TWL4030 family of chips.

	  To compile this driver as a module, choose M here. The module will
	  be called twl4030_pwrbutton.

267 268 269 270 271 272 273 274 275 276 277
config INPUT_TWL4030_VIBRA
	tristate "Support for TWL4030 Vibrator"
	depends on TWL4030_CORE
	select TWL4030_CODEC
	select INPUT_FF_MEMLESS
	help
	  This option enables support for TWL4030 Vibrator Driver.

	  To compile this driver as a module, choose M here. The module will
	  be called twl4030_vibra.

L
Linus Torvalds 已提交
278 279 280 281 282 283 284 285 286
config INPUT_UINPUT
	tristate "User level driver support"
	help
	  Say Y here if you want to support user level drivers for input
	  subsystem accessible under char device 10:223 - /dev/input/uinput.

	  To compile this driver as a module, choose M here: the
	  module will be called uinput.

287 288 289
config INPUT_SGI_BTNS
	tristate "SGI Indy/O2 volume button interface"
	depends on SGI_IP22 || SGI_IP32
290 291
	select INPUT_POLLDEV
	help
292
	  Say Y here if you want to support SGI Indy/O2 volume button interface.
293 294

	  To compile this driver as a module, choose M here: the
295
	  module will be called sgi_btns.
296

297 298 299
config INPUT_WINBOND_CIR
	tristate "Winbond IR remote control"
	depends on X86 && PNP
300
	select NEW_LEDS
301
	select LEDS_CLASS
302
	select LEDS_TRIGGERS
303 304 305 306 307 308 309 310 311 312 313 314
	select BITREVERSE
	help
	  Say Y here if you want to use the IR remote functionality found
	  in some Winbond SuperI/O chips. Currently only the WPCD376I
	  chip is supported (included in some Intel Media series motherboards).

	  IR Receive and wake-on-IR from suspend and power-off is currently
	  supported.

	  To compile this driver as a module, choose M here: the module will be
	  called winbond_cir.

L
Linus Torvalds 已提交
315
config HP_SDC_RTC
316
	tristate "HP SDC Real Time Clock"
317
	depends on (GSC || HP300) && SERIO
L
Linus Torvalds 已提交
318 319 320 321 322
	select HP_SDC
	help
	  Say Y here if you want to support the built-in real time clock
	  of the HP SDC controller.

B
Balaji Rao 已提交
323 324 325 326 327 328 329
config INPUT_PCF50633_PMU
	tristate "PCF50633 PMU events"
	depends on MFD_PCF50633
	help
	 Say Y to include support for delivering  PMU events via  input
	 layer on NXP PCF50633.

330 331 332 333 334 335 336 337 338 339
config INPUT_PCF8574
	tristate "PCF8574 Keypad input device"
	depends on I2C && EXPERIMENTAL
	help
	  Say Y here if you want to support a keypad connetced via I2C
	  with a PCF8574.

	  To compile this driver as a module, choose M here: the
	  module will be called pcf8574_keypad.

340 341 342 343 344 345 346 347 348 349 350
config INPUT_PWM_BEEPER
	tristate "PWM beeper support"
	depends on HAVE_PWM
	help
	  Say Y here to get support for PWM based beeper devices.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the module will be
	  called pwm-beeper.

351 352 353 354 355
config INPUT_GPIO_ROTARY_ENCODER
	tristate "Rotary encoders connected to GPIO pins"
	depends on GPIOLIB && GENERIC_GPIO
	help
	  Say Y here to add support for rotary encoders connected to GPIO lines.
356
	  Check file:Documentation/input/rotary-encoder.txt for more
357 358 359 360 361
	  information.

	  To compile this driver as a module, choose M here: the
	  module will be called rotary_encoder.

362 363 364 365 366 367 368 369 370 371 372 373
config INPUT_RB532_BUTTON
	tristate "Mikrotik Routerboard 532 button interface"
	depends on MIKROTIK_RB532
	depends on GPIOLIB && GENERIC_GPIO
	select INPUT_POLLDEV
	help
	  Say Y here if you want support for the S1 button built into
	  Mikrotik's Routerboard 532.

	  To compile this driver as a module, choose M here: the
	  module will be called rb532_button.

D
David Brownell 已提交
374 375 376
config INPUT_DM355EVM
	tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
	depends on MFD_DM355EVM_MSP
377
	select INPUT_SPARSEKMAP
D
David Brownell 已提交
378 379 380 381 382 383
	help
	  Supports the pushbuttons and IR remote used with
	  the DM355 EVM board.

	  To compile this driver as a module, choose M here: the
	  module will be called dm355evm_keys.
384 385 386 387 388 389 390 391 392 393

config INPUT_BFIN_ROTARY
	tristate "Blackfin Rotary support"
	depends on BF54x || BF52x
	help
	  Say Y here if you want to use the Blackfin Rotary.

	  To compile this driver as a module, choose M here: the
	  module will be called bfin-rotary.

394 395 396 397 398 399 400 401 402 403
config INPUT_WM831X_ON
	tristate "WM831X ON pin"
	depends on MFD_WM831X
	help
	  Support the ON pin of WM831X PMICs as an input device
	  reporting power button status.

	  To compile this driver as a module, choose M here: the module
	  will be called wm831x_on.

D
Daniel Ribeiro 已提交
404 405 406 407 408 409 410 411 412 413
config INPUT_PCAP
	tristate "Motorola EZX PCAP misc input events"
	depends on EZX_PCAP
	help
	  Say Y here if you want to use Power key and Headphone button
	  on Motorola EZX phones.

	  To compile this driver as a module, choose M here: the
	  module will be called pcap_keys.

414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450
config INPUT_ADXL34X
	tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
	default n
	help
	  Say Y here if you have a Accelerometer interface using the
	  ADXL345/6 controller, and your board-specific initialization
	  code includes that in its table of devices.

	  This driver can use either I2C or SPI communication to the
	  ADXL345/6 controller.  Select the appropriate method for
	  your system.

	  If unsure, say N (but it's safe to say "Y").

	  To compile this driver as a module, choose M here: the
	  module will be called adxl34x.

config INPUT_ADXL34X_I2C
	tristate "support I2C bus connection"
	depends on INPUT_ADXL34X && I2C
	default y
	help
	  Say Y here if you have ADXL345/6 hooked to an I2C bus.

	  To compile this driver as a module, choose M here: the
	  module will be called adxl34x-i2c.

config INPUT_ADXL34X_SPI
	tristate "support SPI bus connection"
	depends on INPUT_ADXL34X && SPI
	default y
	help
	  Say Y here if you have ADXL345/6 hooked to a SPI bus.

	  To compile this driver as a module, choose M here: the
	  module will be called adxl34x-spi.

L
Linus Torvalds 已提交
451
endif