1# 2# Input misc drivers configuration 3# 4menuconfig INPUT_MISC 5 bool "Miscellaneous devices" 6 help 7 Say Y here, and a list of miscellaneous input drivers will be displayed. 8 Everything that didn't fit into the other categories is here. This option 9 doesn't affect the kernel. 10 11 If unsure, say Y. 12 13if INPUT_MISC 14 15config INPUT_88PM860X_ONKEY 16 tristate "88PM860x ONKEY support" 17 depends on MFD_88PM860X 18 help 19 Support the ONKEY of Marvell 88PM860x PMICs as an input device 20 reporting power button status. 21 22 To compile this driver as a module, choose M here: the module 23 will be called 88pm860x_onkey. 24 25config INPUT_AB8500_PONKEY 26 tristate "AB8500 Pon (PowerOn) Key" 27 depends on AB8500_CORE 28 help 29 Say Y here to use the PowerOn Key for ST-Ericsson's AB8500 30 Mix-Sig PMIC. 31 32 To compile this driver as a module, choose M here: the module 33 will be called ab8500-ponkey. 34 35config INPUT_AD714X 36 tristate "Analog Devices AD714x Capacitance Touch Sensor" 37 help 38 Say Y here if you want to support an AD7142/3/7/8/7A touch sensor. 39 40 You should select a bus connection too. 41 42 To compile this driver as a module, choose M here: the 43 module will be called ad714x. 44 45config INPUT_AD714X_I2C 46 tristate "support I2C bus connection" 47 depends on INPUT_AD714X && I2C 48 default y 49 help 50 Say Y here if you have AD7142/AD7147 hooked to an I2C bus. 51 52 To compile this driver as a module, choose M here: the 53 module will be called ad714x-i2c. 54 55config INPUT_AD714X_SPI 56 tristate "support SPI bus connection" 57 depends on INPUT_AD714X && SPI 58 default y 59 help 60 Say Y here if you have AD7142/AD7147 hooked to a SPI bus. 61 62 To compile this driver as a module, choose M here: the 63 module will be called ad714x-spi. 64 65config INPUT_BMA150 66 tristate "BMA150/SMB380 acceleration sensor support" 67 depends on I2C 68 select INPUT_POLLDEV 69 help 70 Say Y here if you have Bosch Sensortec's BMA150 or SMB380 71 acceleration sensor hooked to an I2C bus. 72 73 To compile this driver as a module, choose M here: the 74 module will be called bma150. 75 76config INPUT_PCSPKR 77 tristate "PC Speaker support" 78 depends on PCSPKR_PLATFORM 79 help 80 Say Y here if you want the standard PC Speaker to be used for 81 bells and whistles. 82 83 If unsure, say Y. 84 85 To compile this driver as a module, choose M here: the 86 module will be called pcspkr. 87 88config INPUT_PM8XXX_VIBRATOR 89 tristate "Qualcomm PM8XXX vibrator support" 90 depends on MFD_PM8XXX 91 select INPUT_FF_MEMLESS 92 help 93 This option enables device driver support for the vibrator 94 on Qualcomm PM8xxx chip. This driver supports ff-memless interface 95 from input framework. 96 97 To compile this driver as module, choose M here: the 98 module will be called pm8xxx-vibrator. 99 100config INPUT_PMIC8XXX_PWRKEY 101 tristate "PMIC8XXX power key support" 102 depends on MFD_PM8XXX 103 help 104 Say Y here if you want support for the PMIC8XXX power key. 105 106 If unsure, say N. 107 108 To compile this driver as a module, choose M here: the 109 module will be called pmic8xxx-pwrkey. 110 111config INPUT_SPARCSPKR 112 tristate "SPARC Speaker support" 113 depends on PCI && SPARC64 114 help 115 Say Y here if you want the standard Speaker on Sparc PCI systems 116 to be used for bells and whistles. 117 118 If unsure, say Y. 119 120 To compile this driver as a module, choose M here: the 121 module will be called sparcspkr. 122 123config INPUT_M68K_BEEP 124 tristate "M68k Beeper support" 125 depends on M68K 126 127config INPUT_MAX8925_ONKEY 128 tristate "MAX8925 ONKEY support" 129 depends on MFD_MAX8925 130 help 131 Support the ONKEY of MAX8925 PMICs as an input device 132 reporting power button status. 133 134 To compile this driver as a module, choose M here: the module 135 will be called max8925_onkey. 136 137config INPUT_MMA8450 138 tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer" 139 depends on I2C 140 select INPUT_POLLDEV 141 help 142 Say Y here if you want to support Freescale's MMA8450 Accelerometer 143 through I2C interface. 144 145 To compile this driver as a module, choose M here: the 146 module will be called mma8450. 147 148config INPUT_MPU3050 149 tristate "MPU3050 Triaxial gyroscope sensor" 150 depends on I2C 151 help 152 Say Y here if you want to support InvenSense MPU3050 153 connected via an I2C bus. 154 155 To compile this driver as a module, choose M here: the 156 module will be called mpu3050. 157 158config INPUT_APANEL 159 tristate "Fujitsu Lifebook Application Panel buttons" 160 depends on X86 && I2C && LEDS_CLASS 161 select INPUT_POLLDEV 162 select CHECK_SIGNATURE 163 help 164 Say Y here for support of the Application Panel buttons, used on 165 Fujitsu Lifebook. These are attached to the mainboard through 166 an SMBus interface managed by the I2C Intel ICH (i801) driver, 167 which you should also build for this kernel. 168 169 To compile this driver as a module, choose M here: the module will 170 be called apanel. 171 172config INPUT_IXP4XX_BEEPER 173 tristate "IXP4XX Beeper support" 174 depends on ARCH_IXP4XX 175 help 176 If you say yes here, you can connect a beeper to the 177 ixp4xx gpio pins. This is used by the LinkSys NSLU2. 178 179 If unsure, say Y. 180 181 To compile this driver as a module, choose M here: the 182 module will be called ixp4xx-beeper. 183 184config INPUT_COBALT_BTNS 185 tristate "Cobalt button interface" 186 depends on MIPS_COBALT 187 select INPUT_POLLDEV 188 help 189 Say Y here if you want to support MIPS Cobalt button interface. 190 191 To compile this driver as a module, choose M here: the 192 module will be called cobalt_btns. 193 194config INPUT_WISTRON_BTNS 195 tristate "x86 Wistron laptop button interface" 196 depends on X86 && !X86_64 197 select INPUT_POLLDEV 198 select INPUT_SPARSEKMAP 199 select NEW_LEDS 200 select LEDS_CLASS 201 select CHECK_SIGNATURE 202 help 203 Say Y here for support of Wistron laptop button interfaces, used on 204 laptops of various brands, including Acer and Fujitsu-Siemens. If 205 available, mail and wifi LEDs will be controllable via /sys/class/leds. 206 207 To compile this driver as a module, choose M here: the module will 208 be called wistron_btns. 209 210config INPUT_ATLAS_BTNS 211 tristate "x86 Atlas button interface" 212 depends on X86 && ACPI 213 help 214 Say Y here for support of Atlas wallmount touchscreen buttons. 215 The events will show up as scancodes F1 through F9 via evdev. 216 217 To compile this driver as a module, choose M here: the module will 218 be called atlas_btns. 219 220config INPUT_ATI_REMOTE 221 tristate "ATI / X10 USB RF remote control" 222 depends on USB_ARCH_HAS_HCD 223 select USB 224 help 225 Say Y here if you want to use an ATI or X10 "Lola" USB remote control. 226 These are RF remotes with USB receivers. 227 The ATI remote comes with many of ATI's All-In-Wonder video cards. 228 The X10 "Lola" remote is available at: 229 <http://www.x10.com/products/lola_sg1.htm> 230 This driver provides mouse pointer, left and right mouse buttons, 231 and maps all the other remote buttons to keypress events. 232 233 To compile this driver as a module, choose M here: the module will be 234 called ati_remote. 235 236config INPUT_ATI_REMOTE2 237 tristate "ATI / Philips USB RF remote control" 238 depends on USB_ARCH_HAS_HCD 239 select USB 240 help 241 Say Y here if you want to use an ATI or Philips USB RF remote control. 242 These are RF remotes with USB receivers. 243 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards 244 and is also available as a separate product. 245 This driver provides mouse pointer, left and right mouse buttons, 246 and maps all the other remote buttons to keypress events. 247 248 To compile this driver as a module, choose M here: the module will be 249 called ati_remote2. 250 251config INPUT_KEYSPAN_REMOTE 252 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)" 253 depends on EXPERIMENTAL 254 depends on USB_ARCH_HAS_HCD 255 select USB 256 help 257 Say Y here if you want to use a Keyspan DMR USB remote control. 258 Currently only the UIA-11 type of receiver has been tested. The tag 259 on the receiver that connects to the USB port should have a P/N that 260 will tell you what type of DMR you have. The UIA-10 type is not 261 supported at this time. This driver maps all buttons to keypress 262 events. 263 264 To compile this driver as a module, choose M here: the module will 265 be called keyspan_remote. 266 267config INPUT_KXTJ9 268 tristate "Kionix KXTJ9 tri-axis digital accelerometer" 269 depends on I2C 270 help 271 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis 272 accelerometer. 273 274 To compile this driver as a module, choose M here: the module will 275 be called kxtj9. 276 277config INPUT_KXTJ9_POLLED_MODE 278 bool "Enable polling mode support" 279 depends on INPUT_KXTJ9 280 select INPUT_POLLDEV 281 help 282 Say Y here if you need accelerometer to work in polling mode. 283 284config INPUT_POWERMATE 285 tristate "Griffin PowerMate and Contour Jog support" 286 depends on USB_ARCH_HAS_HCD 287 select USB 288 help 289 Say Y here if you want to use Griffin PowerMate or Contour Jog devices. 290 These are aluminum dials which can measure clockwise and anticlockwise 291 rotation. The dial also acts as a pushbutton. The base contains an LED 292 which can be instructed to pulse or to switch to a particular intensity. 293 294 You can download userspace tools from 295 <http://sowerbutts.com/powermate/>. 296 297 To compile this driver as a module, choose M here: the 298 module will be called powermate. 299 300config INPUT_YEALINK 301 tristate "Yealink usb-p1k voip phone" 302 depends on EXPERIMENTAL 303 depends on USB_ARCH_HAS_HCD 304 select USB 305 help 306 Say Y here if you want to enable keyboard and LCD functions of the 307 Yealink usb-p1k usb phones. The audio part is enabled by the generic 308 usb sound driver, so you might want to enable that as well. 309 310 For information about how to use these additional functions, see 311 <file:Documentation/input/yealink.txt>. 312 313 To compile this driver as a module, choose M here: the module will be 314 called yealink. 315 316config INPUT_CM109 317 tristate "C-Media CM109 USB I/O Controller" 318 depends on EXPERIMENTAL 319 depends on USB_ARCH_HAS_HCD 320 select USB 321 help 322 Say Y here if you want to enable keyboard and buzzer functions of the 323 C-Media CM109 usb phones. The audio part is enabled by the generic 324 usb sound driver, so you might want to enable that as well. 325 326 To compile this driver as a module, choose M here: the module will be 327 called cm109. 328 329config INPUT_TWL4030_PWRBUTTON 330 tristate "TWL4030 Power button Driver" 331 depends on TWL4030_CORE 332 help 333 Say Y here if you want to enable power key reporting via the 334 TWL4030 family of chips. 335 336 To compile this driver as a module, choose M here. The module will 337 be called twl4030_pwrbutton. 338 339config INPUT_TWL4030_VIBRA 340 tristate "Support for TWL4030 Vibrator" 341 depends on TWL4030_CORE 342 select MFD_TWL4030_AUDIO 343 select INPUT_FF_MEMLESS 344 help 345 This option enables support for TWL4030 Vibrator Driver. 346 347 To compile this driver as a module, choose M here. The module will 348 be called twl4030_vibra. 349 350config INPUT_TWL6040_VIBRA 351 tristate "Support for TWL6040 Vibrator" 352 depends on TWL4030_CORE 353 select TWL6040_CORE 354 select INPUT_FF_MEMLESS 355 help 356 This option enables support for TWL6040 Vibrator Driver. 357 358 To compile this driver as a module, choose M here. The module will 359 be called twl6040_vibra. 360 361config INPUT_UINPUT 362 tristate "User level driver support" 363 help 364 Say Y here if you want to support user level drivers for input 365 subsystem accessible under char device 10:223 - /dev/input/uinput. 366 367 To compile this driver as a module, choose M here: the 368 module will be called uinput. 369 370config INPUT_SGI_BTNS 371 tristate "SGI Indy/O2 volume button interface" 372 depends on SGI_IP22 || SGI_IP32 373 select INPUT_POLLDEV 374 help 375 Say Y here if you want to support SGI Indy/O2 volume button interface. 376 377 To compile this driver as a module, choose M here: the 378 module will be called sgi_btns. 379 380config HP_SDC_RTC 381 tristate "HP SDC Real Time Clock" 382 depends on (GSC || HP300) && SERIO 383 select HP_SDC 384 help 385 Say Y here if you want to support the built-in real time clock 386 of the HP SDC controller. 387 388config INPUT_PCF50633_PMU 389 tristate "PCF50633 PMU events" 390 depends on MFD_PCF50633 391 help 392 Say Y to include support for delivering PMU events via input 393 layer on NXP PCF50633. 394 395config INPUT_PCF8574 396 tristate "PCF8574 Keypad input device" 397 depends on I2C && EXPERIMENTAL 398 help 399 Say Y here if you want to support a keypad connetced via I2C 400 with a PCF8574. 401 402 To compile this driver as a module, choose M here: the 403 module will be called pcf8574_keypad. 404 405config INPUT_PWM_BEEPER 406 tristate "PWM beeper support" 407 depends on HAVE_PWM 408 help 409 Say Y here to get support for PWM based beeper devices. 410 411 If unsure, say N. 412 413 To compile this driver as a module, choose M here: the module will be 414 called pwm-beeper. 415 416config INPUT_GPIO_ROTARY_ENCODER 417 tristate "Rotary encoders connected to GPIO pins" 418 depends on GPIOLIB && GENERIC_GPIO 419 help 420 Say Y here to add support for rotary encoders connected to GPIO lines. 421 Check file:Documentation/input/rotary-encoder.txt for more 422 information. 423 424 To compile this driver as a module, choose M here: the 425 module will be called rotary_encoder. 426 427config INPUT_RB532_BUTTON 428 tristate "Mikrotik Routerboard 532 button interface" 429 depends on MIKROTIK_RB532 430 depends on GPIOLIB && GENERIC_GPIO 431 select INPUT_POLLDEV 432 help 433 Say Y here if you want support for the S1 button built into 434 Mikrotik's Routerboard 532. 435 436 To compile this driver as a module, choose M here: the 437 module will be called rb532_button. 438 439config INPUT_DM355EVM 440 tristate "TI DaVinci DM355 EVM Keypad and IR Remote" 441 depends on MFD_DM355EVM_MSP 442 select INPUT_SPARSEKMAP 443 help 444 Supports the pushbuttons and IR remote used with 445 the DM355 EVM board. 446 447 To compile this driver as a module, choose M here: the 448 module will be called dm355evm_keys. 449 450config INPUT_BFIN_ROTARY 451 tristate "Blackfin Rotary support" 452 depends on BF54x || BF52x 453 help 454 Say Y here if you want to use the Blackfin Rotary. 455 456 To compile this driver as a module, choose M here: the 457 module will be called bfin-rotary. 458 459config INPUT_WM831X_ON 460 tristate "WM831X ON pin" 461 depends on MFD_WM831X 462 help 463 Support the ON pin of WM831X PMICs as an input device 464 reporting power button status. 465 466 To compile this driver as a module, choose M here: the module 467 will be called wm831x_on. 468 469config INPUT_PCAP 470 tristate "Motorola EZX PCAP misc input events" 471 depends on EZX_PCAP 472 help 473 Say Y here if you want to use Power key and Headphone button 474 on Motorola EZX phones. 475 476 To compile this driver as a module, choose M here: the 477 module will be called pcap_keys. 478 479config INPUT_ADXL34X 480 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer" 481 default n 482 help 483 Say Y here if you have a Accelerometer interface using the 484 ADXL345/6 controller, and your board-specific initialization 485 code includes that in its table of devices. 486 487 This driver can use either I2C or SPI communication to the 488 ADXL345/6 controller. Select the appropriate method for 489 your system. 490 491 If unsure, say N (but it's safe to say "Y"). 492 493 To compile this driver as a module, choose M here: the 494 module will be called adxl34x. 495 496config INPUT_ADXL34X_I2C 497 tristate "support I2C bus connection" 498 depends on INPUT_ADXL34X && I2C 499 default y 500 help 501 Say Y here if you have ADXL345/6 hooked to an I2C bus. 502 503 To compile this driver as a module, choose M here: the 504 module will be called adxl34x-i2c. 505 506config INPUT_ADXL34X_SPI 507 tristate "support SPI bus connection" 508 depends on INPUT_ADXL34X && SPI 509 default y 510 help 511 Say Y here if you have ADXL345/6 hooked to a SPI bus. 512 513 To compile this driver as a module, choose M here: the 514 module will be called adxl34x-spi. 515 516config INPUT_CMA3000 517 tristate "VTI CMA3000 Tri-axis accelerometer" 518 help 519 Say Y here if you want to use VTI CMA3000_D0x Accelerometer 520 driver 521 522 This driver currently only supports I2C interface to the 523 controller. Also select the I2C method. 524 525 If unsure, say N 526 527 To compile this driver as a module, choose M here: the 528 module will be called cma3000_d0x. 529 530config INPUT_CMA3000_I2C 531 tristate "Support I2C bus connection" 532 depends on INPUT_CMA3000 && I2C 533 help 534 Say Y here if you want to use VTI CMA3000_D0x Accelerometer 535 through I2C interface. 536 537 To compile this driver as a module, choose M here: the 538 module will be called cma3000_d0x_i2c. 539 540config INPUT_XEN_KBDDEV_FRONTEND 541 tristate "Xen virtual keyboard and mouse support" 542 depends on XEN_FBDEV_FRONTEND 543 default y 544 select XEN_XENBUS_FRONTEND 545 help 546 This driver implements the front-end of the Xen virtual 547 keyboard and mouse device driver. It communicates with a back-end 548 in another domain. 549 550 To compile this driver as a module, choose M here: the 551 module will be called xen-kbdfront. 552 553endif 554