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