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_88PM80X_ONKEY 26 tristate "88PM80x ONKEY support" 27 depends on MFD_88PM800 28 help 29 Support the ONKEY of Marvell 88PM80x PMICs as an input device 30 reporting power button status. 31 32 To compile this driver as a module, choose M here: the module 33 will be called 88pm80x_onkey. 34 35config INPUT_AB8500_PONKEY 36 tristate "AB8500 Pon (PowerOn) Key" 37 depends on AB8500_CORE 38 help 39 Say Y here to use the PowerOn Key for ST-Ericsson's AB8500 40 Mix-Sig PMIC. 41 42 To compile this driver as a module, choose M here: the module 43 will be called ab8500-ponkey. 44 45config INPUT_AD714X 46 tristate "Analog Devices AD714x Capacitance Touch Sensor" 47 help 48 Say Y here if you want to support an AD7142/3/7/8/7A touch sensor. 49 50 You should select a bus connection too. 51 52 To compile this driver as a module, choose M here: the 53 module will be called ad714x. 54 55config INPUT_AD714X_I2C 56 tristate "support I2C bus connection" 57 depends on INPUT_AD714X && I2C 58 default y 59 help 60 Say Y here if you have AD7142/AD7147 hooked to an I2C bus. 61 62 To compile this driver as a module, choose M here: the 63 module will be called ad714x-i2c. 64 65config INPUT_AD714X_SPI 66 tristate "support SPI bus connection" 67 depends on INPUT_AD714X && SPI 68 default y 69 help 70 Say Y here if you have AD7142/AD7147 hooked to a SPI bus. 71 72 To compile this driver as a module, choose M here: the 73 module will be called ad714x-spi. 74 75config INPUT_ARIZONA_HAPTICS 76 tristate "Arizona haptics support" 77 depends on MFD_ARIZONA && SND_SOC 78 select INPUT_FF_MEMLESS 79 help 80 Say Y to enable support for the haptics module in Arizona CODECs. 81 82 To compile this driver as a module, choose M here: the 83 module will be called arizona-haptics. 84 85config INPUT_BMA150 86 tristate "BMA150/SMB380 acceleration sensor support" 87 depends on I2C 88 select INPUT_POLLDEV 89 help 90 Say Y here if you have Bosch Sensortec's BMA150 or SMB380 91 acceleration sensor hooked to an I2C bus. 92 93 To compile this driver as a module, choose M here: the 94 module will be called bma150. 95 96config INPUT_PCSPKR 97 tristate "PC Speaker support" 98 depends on PCSPKR_PLATFORM 99 help 100 Say Y here if you want the standard PC Speaker to be used for 101 bells and whistles. 102 103 If unsure, say Y. 104 105 To compile this driver as a module, choose M here: the 106 module will be called pcspkr. 107 108config INPUT_PM8XXX_VIBRATOR 109 tristate "Qualcomm PM8XXX vibrator support" 110 depends on MFD_PM8XXX 111 select INPUT_FF_MEMLESS 112 help 113 This option enables device driver support for the vibrator 114 on Qualcomm PM8xxx chip. This driver supports ff-memless interface 115 from input framework. 116 117 To compile this driver as module, choose M here: the 118 module will be called pm8xxx-vibrator. 119 120config INPUT_PMIC8XXX_PWRKEY 121 tristate "PMIC8XXX power key support" 122 depends on MFD_PM8XXX 123 help 124 Say Y here if you want support for the PMIC8XXX power key. 125 126 If unsure, say N. 127 128 To compile this driver as a module, choose M here: the 129 module will be called pmic8xxx-pwrkey. 130 131config INPUT_SPARCSPKR 132 tristate "SPARC Speaker support" 133 depends on PCI && SPARC64 134 help 135 Say Y here if you want the standard Speaker on Sparc PCI systems 136 to be used for bells and whistles. 137 138 If unsure, say Y. 139 140 To compile this driver as a module, choose M here: the 141 module will be called sparcspkr. 142 143config INPUT_M68K_BEEP 144 tristate "M68k Beeper support" 145 depends on M68K 146 147config INPUT_MAX77693_HAPTIC 148 tristate "MAXIM MAX77693 haptic controller support" 149 depends on MFD_MAX77693 && PWM 150 select INPUT_FF_MEMLESS 151 help 152 This option enables support for the haptic controller on 153 MAXIM MAX77693 chip. 154 155 To compile this driver as module, choose M here: the 156 module will be called max77693-haptic. 157 158config INPUT_MAX8925_ONKEY 159 tristate "MAX8925 ONKEY support" 160 depends on MFD_MAX8925 161 help 162 Support the ONKEY of MAX8925 PMICs as an input device 163 reporting power button status. 164 165 To compile this driver as a module, choose M here: the module 166 will be called max8925_onkey. 167 168config INPUT_MAX8997_HAPTIC 169 tristate "MAXIM MAX8997 haptic controller support" 170 depends on PWM && MFD_MAX8997 171 select INPUT_FF_MEMLESS 172 help 173 This option enables device driver support for the haptic controller 174 on MAXIM MAX8997 chip. This driver supports ff-memless interface 175 from input framework. 176 177 To compile this driver as module, choose M here: the 178 module will be called max8997-haptic. 179 180config INPUT_MC13783_PWRBUTTON 181 tristate "MC13783 ON buttons" 182 depends on MFD_MC13XXX 183 help 184 Support the ON buttons of MC13783 PMIC as an input device 185 reporting power button status. 186 187 To compile this driver as a module, choose M here: the module 188 will be called mc13783-pwrbutton. 189 190config INPUT_MMA8450 191 tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer" 192 depends on I2C 193 select INPUT_POLLDEV 194 help 195 Say Y here if you want to support Freescale's MMA8450 Accelerometer 196 through I2C interface. 197 198 To compile this driver as a module, choose M here: the 199 module will be called mma8450. 200 201config INPUT_MPU3050 202 tristate "MPU3050 Triaxial gyroscope sensor" 203 depends on I2C 204 help 205 Say Y here if you want to support InvenSense MPU3050 206 connected via an I2C bus. 207 208 To compile this driver as a module, choose M here: the 209 module will be called mpu3050. 210 211config INPUT_APANEL 212 tristate "Fujitsu Lifebook Application Panel buttons" 213 depends on X86 && I2C && LEDS_CLASS 214 select INPUT_POLLDEV 215 select CHECK_SIGNATURE 216 help 217 Say Y here for support of the Application Panel buttons, used on 218 Fujitsu Lifebook. These are attached to the mainboard through 219 an SMBus interface managed by the I2C Intel ICH (i801) driver, 220 which you should also build for this kernel. 221 222 To compile this driver as a module, choose M here: the module will 223 be called apanel. 224 225config INPUT_GP2A 226 tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver" 227 depends on I2C 228 depends on GPIOLIB 229 help 230 Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip 231 hooked to an I2C bus. 232 233 To compile this driver as a module, choose M here: the 234 module will be called gp2ap002a00f. 235 236config INPUT_GPIO_BEEPER 237 tristate "Generic GPIO Beeper support" 238 depends on GPIOLIB 239 help 240 Say Y here if you have a beeper connected to a GPIO pin. 241 242 To compile this driver as a module, choose M here: the 243 module will be called gpio-beeper. 244 245config INPUT_GPIO_TILT_POLLED 246 tristate "Polled GPIO tilt switch" 247 depends on GPIOLIB 248 select INPUT_POLLDEV 249 help 250 This driver implements support for tilt switches connected 251 to GPIO pins that are not capable of generating interrupts. 252 253 The list of gpios to use and the mapping of their states 254 to specific angles is done via platform data. 255 256 To compile this driver as a module, choose M here: the 257 module will be called gpio_tilt_polled. 258 259config INPUT_IXP4XX_BEEPER 260 tristate "IXP4XX Beeper support" 261 depends on ARCH_IXP4XX 262 help 263 If you say yes here, you can connect a beeper to the 264 ixp4xx gpio pins. This is used by the LinkSys NSLU2. 265 266 If unsure, say Y. 267 268 To compile this driver as a module, choose M here: the 269 module will be called ixp4xx-beeper. 270 271config INPUT_COBALT_BTNS 272 tristate "Cobalt button interface" 273 depends on MIPS_COBALT 274 select INPUT_POLLDEV 275 help 276 Say Y here if you want to support MIPS Cobalt button interface. 277 278 To compile this driver as a module, choose M here: the 279 module will be called cobalt_btns. 280 281config INPUT_WISTRON_BTNS 282 tristate "x86 Wistron laptop button interface" 283 depends on X86_32 284 select INPUT_POLLDEV 285 select INPUT_SPARSEKMAP 286 select NEW_LEDS 287 select LEDS_CLASS 288 select CHECK_SIGNATURE 289 help 290 Say Y here for support of Wistron laptop button interfaces, used on 291 laptops of various brands, including Acer and Fujitsu-Siemens. If 292 available, mail and wifi LEDs will be controllable via /sys/class/leds. 293 294 To compile this driver as a module, choose M here: the module will 295 be called wistron_btns. 296 297config INPUT_ATLAS_BTNS 298 tristate "x86 Atlas button interface" 299 depends on X86 && ACPI 300 help 301 Say Y here for support of Atlas wallmount touchscreen buttons. 302 The events will show up as scancodes F1 through F9 via evdev. 303 304 To compile this driver as a module, choose M here: the module will 305 be called atlas_btns. 306 307config INPUT_ATI_REMOTE2 308 tristate "ATI / Philips USB RF remote control" 309 depends on USB_ARCH_HAS_HCD 310 select USB 311 help 312 Say Y here if you want to use an ATI or Philips USB RF remote control. 313 These are RF remotes with USB receivers. 314 ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards 315 and is also available as a separate product. 316 This driver provides mouse pointer, left and right mouse buttons, 317 and maps all the other remote buttons to keypress events. 318 319 To compile this driver as a module, choose M here: the module will be 320 called ati_remote2. 321 322config INPUT_KEYSPAN_REMOTE 323 tristate "Keyspan DMR USB remote control" 324 depends on USB_ARCH_HAS_HCD 325 select USB 326 help 327 Say Y here if you want to use a Keyspan DMR USB remote control. 328 Currently only the UIA-11 type of receiver has been tested. The tag 329 on the receiver that connects to the USB port should have a P/N that 330 will tell you what type of DMR you have. The UIA-10 type is not 331 supported at this time. This driver maps all buttons to keypress 332 events. 333 334 To compile this driver as a module, choose M here: the module will 335 be called keyspan_remote. 336 337config INPUT_KXTJ9 338 tristate "Kionix KXTJ9 tri-axis digital accelerometer" 339 depends on I2C 340 help 341 Say Y here to enable support for the Kionix KXTJ9 digital tri-axis 342 accelerometer. 343 344 To compile this driver as a module, choose M here: the module will 345 be called kxtj9. 346 347config INPUT_KXTJ9_POLLED_MODE 348 bool "Enable polling mode support" 349 depends on INPUT_KXTJ9 350 select INPUT_POLLDEV 351 help 352 Say Y here if you need accelerometer to work in polling mode. 353 354config INPUT_POWERMATE 355 tristate "Griffin PowerMate and Contour Jog support" 356 depends on USB_ARCH_HAS_HCD 357 select USB 358 help 359 Say Y here if you want to use Griffin PowerMate or Contour Jog devices. 360 These are aluminum dials which can measure clockwise and anticlockwise 361 rotation. The dial also acts as a pushbutton. The base contains an LED 362 which can be instructed to pulse or to switch to a particular intensity. 363 364 You can download userspace tools from 365 <http://sowerbutts.com/powermate/>. 366 367 To compile this driver as a module, choose M here: the 368 module will be called powermate. 369 370config INPUT_YEALINK 371 tristate "Yealink usb-p1k voip phone" 372 depends on USB_ARCH_HAS_HCD 373 select USB 374 help 375 Say Y here if you want to enable keyboard and LCD functions of the 376 Yealink usb-p1k usb phones. The audio part is enabled by the generic 377 usb sound driver, so you might want to enable that as well. 378 379 For information about how to use these additional functions, see 380 <file:Documentation/input/yealink.txt>. 381 382 To compile this driver as a module, choose M here: the module will be 383 called yealink. 384 385config INPUT_CM109 386 tristate "C-Media CM109 USB I/O Controller" 387 depends on USB_ARCH_HAS_HCD 388 select USB 389 help 390 Say Y here if you want to enable keyboard and buzzer functions of the 391 C-Media CM109 usb phones. The audio part is enabled by the generic 392 usb sound driver, so you might want to enable that as well. 393 394 To compile this driver as a module, choose M here: the module will be 395 called cm109. 396 397config INPUT_RETU_PWRBUTTON 398 tristate "Retu Power button Driver" 399 depends on MFD_RETU 400 help 401 Say Y here if you want to enable power key reporting via the 402 Retu chips found in Nokia Internet Tablets (770, N800, N810). 403 404 To compile this driver as a module, choose M here. The module will 405 be called retu-pwrbutton. 406 407config INPUT_TWL4030_PWRBUTTON 408 tristate "TWL4030 Power button Driver" 409 depends on TWL4030_CORE 410 help 411 Say Y here if you want to enable power key reporting via the 412 TWL4030 family of chips. 413 414 To compile this driver as a module, choose M here. The module will 415 be called twl4030_pwrbutton. 416 417config INPUT_TWL4030_VIBRA 418 tristate "Support for TWL4030 Vibrator" 419 depends on TWL4030_CORE 420 select MFD_TWL4030_AUDIO 421 select INPUT_FF_MEMLESS 422 help 423 This option enables support for TWL4030 Vibrator Driver. 424 425 To compile this driver as a module, choose M here. The module will 426 be called twl4030_vibra. 427 428config INPUT_TWL6040_VIBRA 429 tristate "Support for TWL6040 Vibrator" 430 depends on TWL6040_CORE 431 select INPUT_FF_MEMLESS 432 help 433 This option enables support for TWL6040 Vibrator Driver. 434 435 To compile this driver as a module, choose M here. The module will 436 be called twl6040_vibra. 437 438config INPUT_UINPUT 439 tristate "User level driver support" 440 help 441 Say Y here if you want to support user level drivers for input 442 subsystem accessible under char device 10:223 - /dev/input/uinput. 443 444 To compile this driver as a module, choose M here: the 445 module will be called uinput. 446 447config INPUT_SGI_BTNS 448 tristate "SGI Indy/O2 volume button interface" 449 depends on SGI_IP22 || SGI_IP32 450 select INPUT_POLLDEV 451 help 452 Say Y here if you want to support SGI Indy/O2 volume button interface. 453 454 To compile this driver as a module, choose M here: the 455 module will be called sgi_btns. 456 457config HP_SDC_RTC 458 tristate "HP SDC Real Time Clock" 459 depends on (GSC || HP300) && SERIO 460 select HP_SDC 461 help 462 Say Y here if you want to support the built-in real time clock 463 of the HP SDC controller. 464 465config INPUT_PALMAS_PWRBUTTON 466 tristate "Palmas Power button Driver" 467 depends on MFD_PALMAS 468 help 469 Say Y here if you want to enable power key reporting via the 470 Palmas family of PMICs. 471 472 To compile this driver as a module, choose M here. The module will 473 be called palmas_pwrbutton. 474 475config INPUT_PCF50633_PMU 476 tristate "PCF50633 PMU events" 477 depends on MFD_PCF50633 478 help 479 Say Y to include support for delivering PMU events via input 480 layer on NXP PCF50633. 481 482config INPUT_PCF8574 483 tristate "PCF8574 Keypad input device" 484 depends on I2C 485 help 486 Say Y here if you want to support a keypad connected via I2C 487 with a PCF8574. 488 489 To compile this driver as a module, choose M here: the 490 module will be called pcf8574_keypad. 491 492config INPUT_PWM_BEEPER 493 tristate "PWM beeper support" 494 depends on PWM 495 help 496 Say Y here to get support for PWM based beeper devices. 497 498 If unsure, say N. 499 500 To compile this driver as a module, choose M here: the module will be 501 called pwm-beeper. 502 503config INPUT_GPIO_ROTARY_ENCODER 504 tristate "Rotary encoders connected to GPIO pins" 505 depends on GPIOLIB 506 help 507 Say Y here to add support for rotary encoders connected to GPIO lines. 508 Check file:Documentation/input/rotary-encoder.txt for more 509 information. 510 511 To compile this driver as a module, choose M here: the 512 module will be called rotary_encoder. 513 514config INPUT_RB532_BUTTON 515 tristate "Mikrotik Routerboard 532 button interface" 516 depends on MIKROTIK_RB532 517 depends on GPIOLIB 518 select INPUT_POLLDEV 519 help 520 Say Y here if you want support for the S1 button built into 521 Mikrotik's Routerboard 532. 522 523 To compile this driver as a module, choose M here: the 524 module will be called rb532_button. 525 526config INPUT_DA9052_ONKEY 527 tristate "Dialog DA9052/DA9053 Onkey" 528 depends on PMIC_DA9052 529 help 530 Support the ONKEY of Dialog DA9052 PMICs as an input device 531 reporting power button status. 532 533 To compile this driver as a module, choose M here: the 534 module will be called da9052_onkey. 535 536config INPUT_DA9055_ONKEY 537 tristate "Dialog Semiconductor DA9055 ONKEY" 538 depends on MFD_DA9055 539 help 540 Support the ONKEY of DA9055 PMICs as an input device 541 reporting power button status. 542 543 To compile this driver as a module, choose M here: the module 544 will be called da9055_onkey. 545 546config INPUT_DM355EVM 547 tristate "TI DaVinci DM355 EVM Keypad and IR Remote" 548 depends on MFD_DM355EVM_MSP 549 select INPUT_SPARSEKMAP 550 help 551 Supports the pushbuttons and IR remote used with 552 the DM355 EVM board. 553 554 To compile this driver as a module, choose M here: the 555 module will be called dm355evm_keys. 556 557config INPUT_BFIN_ROTARY 558 tristate "Blackfin Rotary support" 559 depends on BF54x || BF52x 560 help 561 Say Y here if you want to use the Blackfin Rotary. 562 563 To compile this driver as a module, choose M here: the 564 module will be called bfin-rotary. 565 566config INPUT_WM831X_ON 567 tristate "WM831X ON pin" 568 depends on MFD_WM831X 569 help 570 Support the ON pin of WM831X PMICs as an input device 571 reporting power button status. 572 573 To compile this driver as a module, choose M here: the module 574 will be called wm831x_on. 575 576config INPUT_PCAP 577 tristate "Motorola EZX PCAP misc input events" 578 depends on EZX_PCAP 579 help 580 Say Y here if you want to use Power key and Headphone button 581 on Motorola EZX phones. 582 583 To compile this driver as a module, choose M here: the 584 module will be called pcap_keys. 585 586config INPUT_ADXL34X 587 tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer" 588 default n 589 help 590 Say Y here if you have a Accelerometer interface using the 591 ADXL345/6 controller, and your board-specific initialization 592 code includes that in its table of devices. 593 594 This driver can use either I2C or SPI communication to the 595 ADXL345/6 controller. Select the appropriate method for 596 your system. 597 598 If unsure, say N (but it's safe to say "Y"). 599 600 To compile this driver as a module, choose M here: the 601 module will be called adxl34x. 602 603config INPUT_ADXL34X_I2C 604 tristate "support I2C bus connection" 605 depends on INPUT_ADXL34X && I2C 606 default y 607 help 608 Say Y here if you have ADXL345/6 hooked to an I2C bus. 609 610 To compile this driver as a module, choose M here: the 611 module will be called adxl34x-i2c. 612 613config INPUT_ADXL34X_SPI 614 tristate "support SPI bus connection" 615 depends on INPUT_ADXL34X && SPI 616 default y 617 help 618 Say Y here if you have ADXL345/6 hooked to a SPI bus. 619 620 To compile this driver as a module, choose M here: the 621 module will be called adxl34x-spi. 622 623config INPUT_IMS_PCU 624 tristate "IMS Passenger Control Unit driver" 625 depends on USB 626 depends on LEDS_CLASS 627 help 628 Say Y here if you have system with IMS Rave Passenger Control Unit. 629 630 To compile this driver as a module, choose M here: the module will be 631 called ims_pcu. 632 633config INPUT_CMA3000 634 tristate "VTI CMA3000 Tri-axis accelerometer" 635 help 636 Say Y here if you want to use VTI CMA3000_D0x Accelerometer 637 driver 638 639 This driver currently only supports I2C interface to the 640 controller. Also select the I2C method. 641 642 If unsure, say N 643 644 To compile this driver as a module, choose M here: the 645 module will be called cma3000_d0x. 646 647config INPUT_CMA3000_I2C 648 tristate "Support I2C bus connection" 649 depends on INPUT_CMA3000 && I2C 650 help 651 Say Y here if you want to use VTI CMA3000_D0x Accelerometer 652 through I2C interface. 653 654 To compile this driver as a module, choose M here: the 655 module will be called cma3000_d0x_i2c. 656 657config INPUT_XEN_KBDDEV_FRONTEND 658 tristate "Xen virtual keyboard and mouse support" 659 depends on XEN 660 default y 661 select XEN_XENBUS_FRONTEND 662 help 663 This driver implements the front-end of the Xen virtual 664 keyboard and mouse device driver. It communicates with a back-end 665 in another domain. 666 667 To compile this driver as a module, choose M here: the 668 module will be called xen-kbdfront. 669 670config INPUT_SIRFSOC_ONKEY 671 bool "CSR SiRFSoC power on/off/suspend key support" 672 depends on ARCH_SIRF && OF 673 default y 674 help 675 Say Y here if you want to support for the SiRFSoC power on/off/suspend key 676 in Linux, after you press the onkey, system will suspend. 677 678 If unsure, say N. 679 680config INPUT_IDEAPAD_SLIDEBAR 681 tristate "IdeaPad Laptop Slidebar" 682 depends on INPUT 683 depends on SERIO_I8042 684 help 685 Say Y here if you have an IdeaPad laptop with a slidebar. 686 687 To compile this driver as a module, choose M here: the 688 module will be called ideapad_slidebar. 689 690config INPUT_SOC_BUTTON_ARRAY 691 tristate "Windows-compatible SoC Button Array" 692 depends on KEYBOARD_GPIO 693 help 694 Say Y here if you have a SoC-based tablet that originally 695 runs Windows 8. 696 697 To compile this driver as a module, choose M here: the 698 module will be called soc_button_array. 699 700config INPUT_DRV260X_HAPTICS 701 tristate "TI DRV260X haptics support" 702 depends on INPUT && I2C && GPIOLIB 703 select INPUT_FF_MEMLESS 704 select REGMAP_I2C 705 help 706 Say Y to enable support for the TI DRV260X haptics driver. 707 708 To compile this driver as a module, choose M here: the 709 module will be called drv260x-haptics. 710 711config INPUT_DRV2667_HAPTICS 712 tristate "TI DRV2667 haptics support" 713 depends on INPUT && I2C 714 select INPUT_FF_MEMLESS 715 select REGMAP_I2C 716 help 717 Say Y to enable support for the TI DRV2667 haptics driver. 718 719 To compile this driver as a module, choose M here: the 720 module will be called drv260x-haptics. 721 722endif 723