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