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