Kconfig

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