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_MAX8997_HAPTIC 138 tristate "MAXIM MAX8997 haptic controller support" 139 depends on HAVE_PWM && MFD_MAX8997 140 select INPUT_FF_MEMLESS 141 help 142 This option enables device driver support for the haptic controller 143 on MAXIM MAX8997 chip. This driver supports ff-memless interface 144 from input framework. 145 146 To compile this driver as module, choose M here: the 147 module will be called max8997-haptic. 148 149config INPUT_MC13783_PWRBUTTON 150 tristate "MC13783 ON buttons" 151 depends on MFD_MC13783 152 help 153 Support the ON buttons of MC13783 PMIC as an input device 154 reporting power button status. 155 156 To compile this driver as a module, choose M here: the module 157 will be called mc13783-pwrbutton. 158 159config INPUT_MMA8450 160 tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer" 161 depends on I2C 162 select INPUT_POLLDEV 163 help 164 Say Y here if you want to support Freescale's MMA8450 Accelerometer 165 through I2C interface. 166 167 To compile this driver as a module, choose M here: the 168 module will be called mma8450. 169 170config INPUT_MPU3050 171 tristate "MPU3050 Triaxial gyroscope sensor" 172 depends on I2C 173 help 174 Say Y here if you want to support InvenSense MPU3050 175 connected via an I2C bus. 176 177 To compile this driver as a module, choose M here: the 178 module will be called mpu3050. 179 180config INPUT_APANEL 181 tristate "Fujitsu Lifebook Application Panel buttons" 182 depends on X86 && I2C && LEDS_CLASS 183 select INPUT_POLLDEV 184 select CHECK_SIGNATURE 185 help 186 Say Y here for support of the Application Panel buttons, used on 187 Fujitsu Lifebook. These are attached to the mainboard through 188 an SMBus interface managed by the I2C Intel ICH (i801) driver, 189 which you should also build for this kernel. 190 191 To compile this driver as a module, choose M here: the module will 192 be called apanel. 193 194config INPUT_GP2A 195 tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver" 196 depends on I2C 197 depends on GENERIC_GPIO 198 help 199 Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip 200 hooked to an I2C bus. 201 202 To compile this driver as a module, choose M here: the 203 module will be called gp2ap002a00f. 204 205config INPUT_GPIO_TILT_POLLED 206 tristate "Polled GPIO tilt switch" 207 depends on GENERIC_GPIO 208 select INPUT_POLLDEV 209 help 210 This driver implements support for tilt switches connected 211 to GPIO pins that are not capable of generating interrupts. 212 213 The list of gpios to use and the mapping of their states 214 to specific angles is done via platform data. 215 216 To compile this driver as a module, choose M here: the 217 module will be called gpio_tilt_polled. 218 219config INPUT_IXP4XX_BEEPER 220 tristate "IXP4XX Beeper support" 221 depends on ARCH_IXP4XX 222 help 223 If you say yes here, you can connect a beeper to the 224 ixp4xx gpio pins. This is used by the LinkSys NSLU2. 225 226 If unsure, say Y. 227 228 To compile this driver as a module, choose M here: the 229 module will be called ixp4xx-beeper. 230 231config INPUT_COBALT_BTNS 232 tristate "Cobalt button interface" 233 depends on MIPS_COBALT 234 select INPUT_POLLDEV 235 help 236 Say Y here if you want to support MIPS Cobalt button interface. 237 238 To compile this driver as a module, choose M here: the 239 module will be called cobalt_btns. 240 241config INPUT_WISTRON_BTNS 242 tristate "x86 Wistron laptop button interface" 243 depends on X86 && !X86_64 244 select INPUT_POLLDEV 245 select INPUT_SPARSEKMAP 246 select NEW_LEDS 247 select LEDS_CLASS 248 select CHECK_SIGNATURE 249 help 250 Say Y here for support of Wistron laptop button interfaces, used on 251 laptops of various brands, including Acer and Fujitsu-Siemens. If 252 available, mail and wifi LEDs will be controllable via /sys/class/leds. 253 254 To compile this driver as a module, choose M here: the module will 255 be called wistron_btns. 256 257config INPUT_ATLAS_BTNS 258 tristate "x86 Atlas button interface" 259 depends on X86 && ACPI 260 help 261 Say Y here for support of Atlas wallmount touchscreen buttons. 262 The events will show up as scancodes F1 through F9 via evdev. 263 264 To compile this driver as a module, choose M here: the module will 265 be called atlas_btns. 266 267config INPUT_ATI_REMOTE2 268 tristate "ATI / Philips USB RF remote control" 269 depends on USB_ARCH_HAS_HCD 270 select USB 271 help 272 Say Y here if you want to use an ATI or Philips USB RF remote control. 273 These are RF remotes with USB receivers. 274 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards 275 and is also available as a separate product. 276 This driver provides mouse pointer, left and right mouse buttons, 277 and maps all the other remote buttons to keypress events. 278 279 To compile this driver as a module, choose M here: the module will be 280 called ati_remote2. 281 282config INPUT_KEYSPAN_REMOTE 283 tristate "Keyspan DMR USB remote control (EXPERIMENTAL)" 284 depends on EXPERIMENTAL 285 depends on USB_ARCH_HAS_HCD 286 select USB 287 help 288 Say Y here if you want to use a Keyspan DMR USB remote control. 289 Currently only the UIA-11 type of receiver has been tested. The tag 290 on the receiver that connects to the USB port should have a P/N that 291 will tell you what type of DMR you have. The UIA-10 type is not 292 supported at this time. This driver maps all buttons to keypress 293 events. 294 295 To compile this driver as a module, choose M here: the module will 296 be called keyspan_remote. 297 298config INPUT_KXTJ9 299 tristate "Kionix KXTJ9 tri-axis digital accelerometer" 300 depends on I2C 301 help 302 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis 303 accelerometer. 304 305 To compile this driver as a module, choose M here: the module will 306 be called kxtj9. 307 308config INPUT_KXTJ9_POLLED_MODE 309 bool "Enable polling mode support" 310 depends on INPUT_KXTJ9 311 select INPUT_POLLDEV 312 help 313 Say Y here if you need accelerometer to work in polling mode. 314 315config INPUT_POWERMATE 316 tristate "Griffin PowerMate and Contour Jog support" 317 depends on USB_ARCH_HAS_HCD 318 select USB 319 help 320 Say Y here if you want to use Griffin PowerMate or Contour Jog devices. 321 These are aluminum dials which can measure clockwise and anticlockwise 322 rotation. The dial also acts as a pushbutton. The base contains an LED 323 which can be instructed to pulse or to switch to a particular intensity. 324 325 You can download userspace tools from 326 <http://sowerbutts.com/powermate/>. 327 328 To compile this driver as a module, choose M here: the 329 module will be called powermate. 330 331config INPUT_YEALINK 332 tristate "Yealink usb-p1k voip phone" 333 depends on EXPERIMENTAL 334 depends on USB_ARCH_HAS_HCD 335 select USB 336 help 337 Say Y here if you want to enable keyboard and LCD functions of the 338 Yealink usb-p1k usb phones. The audio part is enabled by the generic 339 usb sound driver, so you might want to enable that as well. 340 341 For information about how to use these additional functions, see 342 <file:Documentation/input/yealink.txt>. 343 344 To compile this driver as a module, choose M here: the module will be 345 called yealink. 346 347config INPUT_CM109 348 tristate "C-Media CM109 USB I/O Controller" 349 depends on EXPERIMENTAL 350 depends on USB_ARCH_HAS_HCD 351 select USB 352 help 353 Say Y here if you want to enable keyboard and buzzer functions of the 354 C-Media CM109 usb phones. The audio part is enabled by the generic 355 usb sound driver, so you might want to enable that as well. 356 357 To compile this driver as a module, choose M here: the module will be 358 called cm109. 359 360config INPUT_TWL4030_PWRBUTTON 361 tristate "TWL4030 Power button Driver" 362 depends on TWL4030_CORE 363 help 364 Say Y here if you want to enable power key reporting via the 365 TWL4030 family of chips. 366 367 To compile this driver as a module, choose M here. The module will 368 be called twl4030_pwrbutton. 369 370config INPUT_TWL4030_VIBRA 371 tristate "Support for TWL4030 Vibrator" 372 depends on TWL4030_CORE 373 select MFD_TWL4030_AUDIO 374 select INPUT_FF_MEMLESS 375 help 376 This option enables support for TWL4030 Vibrator Driver. 377 378 To compile this driver as a module, choose M here. The module will 379 be called twl4030_vibra. 380 381config INPUT_TWL6040_VIBRA 382 tristate "Support for TWL6040 Vibrator" 383 depends on TWL6040_CORE 384 select INPUT_FF_MEMLESS 385 help 386 This option enables support for TWL6040 Vibrator Driver. 387 388 To compile this driver as a module, choose M here. The module will 389 be called twl6040_vibra. 390 391config INPUT_UINPUT 392 tristate "User level driver support" 393 help 394 Say Y here if you want to support user level drivers for input 395 subsystem accessible under char device 10:223 - /dev/input/uinput. 396 397 To compile this driver as a module, choose M here: the 398 module will be called uinput. 399 400config INPUT_SGI_BTNS 401 tristate "SGI Indy/O2 volume button interface" 402 depends on SGI_IP22 || SGI_IP32 403 select INPUT_POLLDEV 404 help 405 Say Y here if you want to support SGI Indy/O2 volume button interface. 406 407 To compile this driver as a module, choose M here: the 408 module will be called sgi_btns. 409 410config HP_SDC_RTC 411 tristate "HP SDC Real Time Clock" 412 depends on (GSC || HP300) && SERIO 413 select HP_SDC 414 help 415 Say Y here if you want to support the built-in real time clock 416 of the HP SDC controller. 417 418config INPUT_PCF50633_PMU 419 tristate "PCF50633 PMU events" 420 depends on MFD_PCF50633 421 help 422 Say Y to include support for delivering PMU events via input 423 layer on NXP PCF50633. 424 425config INPUT_PCF8574 426 tristate "PCF8574 Keypad input device" 427 depends on I2C && EXPERIMENTAL 428 help 429 Say Y here if you want to support a keypad connected via I2C 430 with a PCF8574. 431 432 To compile this driver as a module, choose M here: the 433 module will be called pcf8574_keypad. 434 435config INPUT_PWM_BEEPER 436 tristate "PWM beeper support" 437 depends on HAVE_PWM 438 help 439 Say Y here to get support for PWM based beeper devices. 440 441 If unsure, say N. 442 443 To compile this driver as a module, choose M here: the module will be 444 called pwm-beeper. 445 446config INPUT_GPIO_ROTARY_ENCODER 447 tristate "Rotary encoders connected to GPIO pins" 448 depends on GPIOLIB && GENERIC_GPIO 449 help 450 Say Y here to add support for rotary encoders connected to GPIO lines. 451 Check file:Documentation/input/rotary-encoder.txt for more 452 information. 453 454 To compile this driver as a module, choose M here: the 455 module will be called rotary_encoder. 456 457config INPUT_RB532_BUTTON 458 tristate "Mikrotik Routerboard 532 button interface" 459 depends on MIKROTIK_RB532 460 depends on GPIOLIB && GENERIC_GPIO 461 select INPUT_POLLDEV 462 help 463 Say Y here if you want support for the S1 button built into 464 Mikrotik's Routerboard 532. 465 466 To compile this driver as a module, choose M here: the 467 module will be called rb532_button. 468 469config INPUT_DA9052_ONKEY 470 tristate "Dialog DA9052/DA9053 Onkey" 471 depends on PMIC_DA9052 472 help 473 Support the ONKEY of Dialog DA9052 PMICs as an input device 474 reporting power button status. 475 476 To compile this driver as a module, choose M here: the 477 module will be called da9052_onkey. 478 479config INPUT_DM355EVM 480 tristate "TI DaVinci DM355 EVM Keypad and IR Remote" 481 depends on MFD_DM355EVM_MSP 482 select INPUT_SPARSEKMAP 483 help 484 Supports the pushbuttons and IR remote used with 485 the DM355 EVM board. 486 487 To compile this driver as a module, choose M here: the 488 module will be called dm355evm_keys. 489 490config INPUT_BFIN_ROTARY 491 tristate "Blackfin Rotary support" 492 depends on BF54x || BF52x 493 help 494 Say Y here if you want to use the Blackfin Rotary. 495 496 To compile this driver as a module, choose M here: the 497 module will be called bfin-rotary. 498 499config INPUT_WM831X_ON 500 tristate "WM831X ON pin" 501 depends on MFD_WM831X 502 help 503 Support the ON pin of WM831X PMICs as an input device 504 reporting power button status. 505 506 To compile this driver as a module, choose M here: the module 507 will be called wm831x_on. 508 509config INPUT_PCAP 510 tristate "Motorola EZX PCAP misc input events" 511 depends on EZX_PCAP 512 help 513 Say Y here if you want to use Power key and Headphone button 514 on Motorola EZX phones. 515 516 To compile this driver as a module, choose M here: the 517 module will be called pcap_keys. 518 519config INPUT_ADXL34X 520 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer" 521 default n 522 help 523 Say Y here if you have a Accelerometer interface using the 524 ADXL345/6 controller, and your board-specific initialization 525 code includes that in its table of devices. 526 527 This driver can use either I2C or SPI communication to the 528 ADXL345/6 controller. Select the appropriate method for 529 your system. 530 531 If unsure, say N (but it's safe to say "Y"). 532 533 To compile this driver as a module, choose M here: the 534 module will be called adxl34x. 535 536config INPUT_ADXL34X_I2C 537 tristate "support I2C bus connection" 538 depends on INPUT_ADXL34X && I2C 539 default y 540 help 541 Say Y here if you have ADXL345/6 hooked to an I2C bus. 542 543 To compile this driver as a module, choose M here: the 544 module will be called adxl34x-i2c. 545 546config INPUT_ADXL34X_SPI 547 tristate "support SPI bus connection" 548 depends on INPUT_ADXL34X && SPI 549 default y 550 help 551 Say Y here if you have ADXL345/6 hooked to a SPI bus. 552 553 To compile this driver as a module, choose M here: the 554 module will be called adxl34x-spi. 555 556config INPUT_CMA3000 557 tristate "VTI CMA3000 Tri-axis accelerometer" 558 help 559 Say Y here if you want to use VTI CMA3000_D0x Accelerometer 560 driver 561 562 This driver currently only supports I2C interface to the 563 controller. Also select the I2C method. 564 565 If unsure, say N 566 567 To compile this driver as a module, choose M here: the 568 module will be called cma3000_d0x. 569 570config INPUT_CMA3000_I2C 571 tristate "Support I2C bus connection" 572 depends on INPUT_CMA3000 && I2C 573 help 574 Say Y here if you want to use VTI CMA3000_D0x Accelerometer 575 through I2C interface. 576 577 To compile this driver as a module, choose M here: the 578 module will be called cma3000_d0x_i2c. 579 580config INPUT_XEN_KBDDEV_FRONTEND 581 tristate "Xen virtual keyboard and mouse support" 582 depends on XEN 583 default y 584 select XEN_XENBUS_FRONTEND 585 help 586 This driver implements the front-end of the Xen virtual 587 keyboard and mouse device driver. It communicates with a back-end 588 in another domain. 589 590 To compile this driver as a module, choose M here: the 591 module will be called xen-kbdfront. 592 593endif 594