Kconfig - OpenGrok cross reference for /linux-6.12.1/drivers/input/misc/Kconfig

1 # SPDX-License-Identifier: GPL-2.0-only
21 	  reporting power button status.
31 	  reporting power button status.
41 	  reporting power button status.
47 	  Say Y here to use the PowerOn Key for ST-Ericsson's AB8500
48 	  Mix-Sig PMIC.
51 	  will be called ab8500-ponkey.
71 	  module will be called ad714x-i2c.
81 	  module will be called ad714x-spi.
84 	tristate "Dell Wyse 3020 Power Button Driver"
88 	  Say Y to enable support for reporting power button status on
92 	  will be called ariel-pwrbutton.
99 	  Say Y to enable support for the haptics module in Arizona CODECs.
102 	  module will be called arizona-haptics.
109 	  power button status. ONKEY can be used to wakeup from low power
113 	  module will be called atc260x-onkey.
130 	tristate "NXP BBNSM Power Key Driver"
134 	  This is the bbnsm powerkey driver for the NXP i.MX application
154 	  Say Y here to enable support for Cirrus Logic's CS40L50
158 	  module will be called cs40l50-vibra.
164 	  Say Y here to enable support for the NI Ettus Research
174 	  Say Y here if you want the standard PC Speaker to be used for
183 	tristate "Qualcomm PM8941 power key support"
186 	  Say Y here if you want support for the power key usually found
192 	  will be called pm8941-pwrkey.
199 	  This option enables device driver support for the vibrator
200 	  on Qualcomm PM8xxx chip. This driver supports ff-memless interface
204 	  module will be called pm8xxx-vibrator.
207 	tristate "PMIC8XXX power key support"
210 	  Say Y here if you want support for the PMIC8XXX power key.
215 	  module will be called pmic8xxx-pwrkey.
222 	  to be used for bells and whistles.
240 	  will be called max77650-onkey.
247 	  This option enables support for the haptic controller on
251 	  module will be called max77693-haptic.
258 	  reporting power button status.
268 	  This option enables device driver support for the haptic controller
269 	  on MAXIM MAX8997 chip. This driver supports ff-memless interface
273 	  module will be called max8997-haptic.
280 	  reporting power button status.
283 	  will be called mc13783-pwrbutton.
286 	tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
300 	 Say Y here for support of the Application Panel buttons, used on
303 	 which you should also build for this kernel.
315 	  module will be called gpio-beeper.
333 	  Say Y here to get support for GPIO based vibrator devices.
338 	  called gpio-vibra.
353 	  Say Y here if you want to enable power key reporting via the
357 	  be called cpcap-pwrbutton.
367 	  Say Y here for support of Wistron laptop button interfaces, used on
368 	  laptops of various brands, including Acer and Fujitsu-Siemens. If
378 	  Say Y here for support of Atlas wallmount touchscreen buttons.
391 	  ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
405 	  Currently only the UIA-11 type of receiver has been tested.  The tag
407 	  will tell you what type of DMR you have.  The UIA-10 type is not
415 	tristate "Kionix KXTJ9 tri-axis digital accelerometer"
418 	  Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
441 	tristate "Yealink usb-p1k voip phone"
446 	  Yealink usb-p1k usb phones. The audio part is enabled by the generic
449 	  For information about how to use these additional functions, see
456 	tristate "C-Media CM109 USB I/O Controller"
461 	  C-Media CM109 usb phones. The audio part is enabled by the generic
472 	  This option enables device driver support for the haptic controlled
473 	  by a regulator. This driver supports ff-memless interface
477 	  module will be called regulator-haptic.
480 	tristate "Retu Power button Driver"
483 	  Say Y here if you want to enable power key reporting via the
487 	  be called retu-pwrbutton.
490 	tristate "TPS65218 Power button driver"
493 	  Say Y here if you want to enable power button reporting for
494 	  TPS65217 and TPS65218 Power Management IC devices.
497 	  be called tps65218-pwrbutton.
500 	tristate "TPS65219 Power button driver"
503 	  Say Y here if you want to enable power button reporting for
504 	  TPS65219 Power Management IC devices.
507 	  be called tps65219-pwrbutton.
510 	tristate "X-Powers AXP20X power button driver"
513 	  Say Y here if you want to enable power key reporting via the
517 	  be called axp20x-pek.
521 	tristate "TWL4030 Power button Driver"
524 	  Say Y here if you want to enable power key reporting via the
531 	tristate "Support for TWL4030 Vibrator"
536 	  This option enables support for TWL4030 Vibrator Driver.
542 	tristate "Support for TWL6040 Vibrator"
546 	  This option enables support for TWL6040 Vibrator Driver.
554 	  Say Y here if you want to support user level drivers for input
555 	  subsystem accessible under char device 10:223 - /dev/input/uinput.
574 	  Say Y here if you want to support the built-in real time clock
578 	tristate "Palmas Power button Driver"
581 	  Say Y here if you want to enable power key reporting via the
591 	 Say Y to include support for delivering  PMU events via  input
608 	  Say Y here to get support for PWM based beeper devices.
613 	  called pwm-beeper.
620 	  Say Y here to get support for PWM based vibrator devices.
625 	  called pwm-vibra.
628 	tristate "Rockchip RK805 PMIC power key support"
631 	  Select this option to enable power key driver for RK805.
642 	  Say Y here to add support for rotary encoders connected to GPIO lines.
643 	  Check file:Documentation/input/devices/rotary-encoder.rst for more
654 	  Say Y here if you want support for the S1 button built into
665 	  Say Y to enable support for the Dialog DA7280 haptics driver.
677 	  reporting power button status.
687 	  reporting power button status.
696 	  Support the ONKEY of Dialog DA9063, DA9062 and DA9061 Power
697 	  Management ICs as an input device capable of reporting the
698 	  power button status.
708 	  reporting power button status.
717 	  Say Y here if you want to use Power key and Headphone button
724 	tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
728 	  ADXL345/6 controller, and your board-specific initialization
732 	  ADXL345/6 controller.  Select the appropriate method for
733 	  your system.
748 	  module will be called adxl34x-i2c.
758 	  module will be called adxl34x-spi.
764 	  Say Y here if you have an IBM Operation Panel connected to your system
765 	  over I2C. The panel is typically connected only to a system's service
771 	  display that allows someone with physical access to the system to
773 	  of the controller that sends commands to the system.
776 	  called ibm-panel.
783 	  Say Y here if you have system with IMS Rave Passenger Control Unit.
793 	  Say Y to enable support for the Azoteq IQS269A capacitive
804 	  Say Y to enable support for the Azoteq IQS626A capacitive
814 	  Say Y to enable support for the Azoteq IQS7222A/B/C/D family
821 	tristate "VTI CMA3000 Tri-axis accelerometer"
850 	  This driver implements the front-end of the Xen virtual
851 	  keyboard and mouse device driver.  It communicates with a back-end
855 	  module will be called xen-kbdfront.
868 	tristate "Windows-compatible SoC Button Array"
871 	  Say Y here if you have a SoC-based tablet that originally runs
884 	  Say Y to enable support for the TI DRV260X haptics driver.
887 	  module will be called drv260x-haptics.
895 	  Say Y to enable support for the TI DRV2665 haptics driver.
898 	  module will be called drv2665-haptics.
906 	  Say Y to enable support for the TI DRV2667 haptics driver.
909 	  module will be called drv2667-haptics.
915 	  Say Y to enable support for PMIC ONKEY.
921 	tristate "RAVE SP Power button Driver"
924 	  Say Y here if you want to enable power key reporting from RAVE SP
927 	  module will be called rave-sp-pwrbutton.
934 	  This option enables support for Spreadtrum sc27xx vibrator driver.
940 	tristate "RT5120 PMIC power key support"
943 	  This enables support for RT5120 PMIC power key driver.
946 	  be called rt5120-pwrkey.
953 	  can be used to wakeup from low power modes and force a shut-down on