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