#
# Input misc drivers configuration
#
menuconfig [31mCONFIG_INPUT_MISC[0m
bool "Miscellaneous devices"
help
Say Y here, and a list of miscellaneous input drivers will be displayed.
Everything that didn't fit into the other categories is here. This option
doesn't affect the kernel.
If unsure, say Y.
if [31mCONFIG_INPUT_MISC[0m
config [31mCONFIG_INPUT_88PM860X_ONKEY[0m
tristate "88PM860x ONKEY support"
depends on [31mCONFIG_MFD_88PM860X[0m
help
Support the ONKEY of Marvell 88PM860x PMICs as an input device
reporting power button status.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called 88pm860x_onkey.
config [31mCONFIG_INPUT_88PM80X_ONKEY[0m
tristate "88PM80x ONKEY support"
depends on [31mCONFIG_MFD_88PM800[0m
help
Support the ONKEY of Marvell 88PM80x PMICs as an input device
reporting power button status.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called 88pm80x_onkey.
config [31mCONFIG_INPUT_AB8500_PONKEY[0m
tristate "AB8500 Pon (PowerOn) Key"
depends on [31mCONFIG_AB8500_CORE[0m
help
Say Y here to use the PowerOn Key for ST-Ericsson's AB8500
Mix-Sig PMIC.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called ab8500-ponkey.
config [31mCONFIG_INPUT_AD714X[0m
tristate "Analog Devices AD714x Capacitance Touch Sensor"
help
Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
You should select a bus connection too.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ad714x.
config [31mCONFIG_INPUT_AD714X_I2C[0m
tristate "support I2C bus connection"
depends on [31mCONFIG_INPUT_AD714X[0m && [31mCONFIG_I2C[0m
default y
help
Say Y here if you have AD7142/AD7147 hooked to an [31mCONFIG_I2C[0m bus.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ad714x-i2c.
config [31mCONFIG_INPUT_AD714X_SPI[0m
tristate "support SPI bus connection"
depends on [31mCONFIG_INPUT_AD714X[0m && [31mCONFIG_SPI[0m
default y
help
Say Y here if you have AD7142/AD7147 hooked to a [31mCONFIG_SPI[0m bus.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ad714x-spi.
config [31mCONFIG_INPUT_ARIZONA_HAPTICS[0m
tristate "Arizona haptics support"
depends on [31mCONFIG_MFD_ARIZONA[0m && [31mCONFIG_SND_SOC[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
help
Say Y to enable support for the haptics module in Arizona CODECs.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called arizona-haptics.
config [31mCONFIG_INPUT_ATMEL_CAPTOUCH[0m
tristate "Atmel Capacitive Touch Button Driver"
depends on [31mCONFIG_OF[0m || [31mCONFIG_COMPILE_TEST[0m
depends on [31mCONFIG_I2C[0m
help
Say Y here if an Atmel Capacitive Touch Button device which
implements "captouch" protocol is connected to [31mCONFIG_I2C[0m bus. Typically
this device consists of Atmel Touch sensor controlled by AtMegaXX
MCU running firmware based on Qtouch library.
One should find "atmel,captouch" node in the board specific DTS.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called atmel_captouch.
config [31mCONFIG_INPUT_BMA150[0m
tristate "BMA150/SMB380 acceleration sensor support"
depends on [31mCONFIG_I2C[0m
select [31mCONFIG_INPUT_POLLDEV[0m
help
Say Y here if you have Bosch Sensortec's BMA150 or SMB380
acceleration sensor hooked to an [31mCONFIG_I2C[0m bus.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called bma150.
config [31mCONFIG_INPUT_E3X0_BUTTON[0m
tristate "NI Ettus Research USRP E3xx Button support."
default n
help
Say Y here to enable support for the NI Ettus Research
USRP E3xx Button.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called e3x0_button.
config [31mCONFIG_INPUT_PCSPKR[0m
tristate "PC Speaker support"
depends on [31mCONFIG_PCSPKR_PLATFORM[0m
help
Say Y here if you want the standard PC Speaker to be used for
bells and whistles.
If unsure, say Y.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called pcspkr.
config [31mCONFIG_INPUT_PM8941_PWRKEY[0m
tristate "Qualcomm PM8941 power key support"
depends on [31mCONFIG_MFD_SPMI_PMIC[0m
help
Say Y here if you want support for the power key usually found
on boards using a Qualcomm PM8941 compatible PMIC.
If unsure, say Y.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called pm8941-pwrkey.
config [31mCONFIG_INPUT_PM8XXX_VIBRATOR[0m
tristate "Qualcomm PM8XXX vibrator support"
depends on [31mCONFIG_MFD_PM8XXX[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
help
This option enables device driver support for the vibrator
on Qualcomm PM8xxx chip. This driver supports ff-memless interface
from input framework.
To compile this driver as module, choose [31mCONFIG_M[0m here: the
module will be called pm8xxx-vibrator.
config [31mCONFIG_INPUT_PMIC8XXX_PWRKEY[0m
tristate "PMIC8XXX power key support"
depends on [31mCONFIG_MFD_PM8XXX[0m
help
Say Y here if you want support for the PMIC8XXX power key.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called pmic8xxx-pwrkey.
config [31mCONFIG_INPUT_SPARCSPKR[0m
tristate "SPARC Speaker support"
depends on [31mCONFIG_PCI[0m && [31mCONFIG_SPARC64[0m
help
Say Y here if you want the standard Speaker on Sparc [31mCONFIG_PCI[0m systems
to be used for bells and whistles.
If unsure, say Y.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called sparcspkr.
config [31mCONFIG_INPUT_M68K_BEEP[0m
tristate "M68k Beeper support"
depends on [31mCONFIG_M68K[0m
config [31mCONFIG_INPUT_MAX77693_HAPTIC[0m
tristate "MAXIM MAX77693/MAX77843 haptic controller support"
depends on ([31mCONFIG_MFD_MAX77693[0m || [31mCONFIG_MFD_MAX77843[0m) && [31mCONFIG_PWM[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
help
This option enables support for the haptic controller on
MAXIM MAX77693 and MAX77843 chips.
To compile this driver as module, choose [31mCONFIG_M[0m here: the
module will be called max77693-haptic.
config [31mCONFIG_INPUT_MAX8925_ONKEY[0m
tristate "MAX8925 ONKEY support"
depends on [31mCONFIG_MFD_MAX8925[0m
help
Support the ONKEY of MAX8925 PMICs as an input device
reporting power button status.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called max8925_onkey.
config [31mCONFIG_INPUT_MAX8997_HAPTIC[0m
tristate "MAXIM MAX8997 haptic controller support"
depends on [31mCONFIG_PWM[0m && [31mCONFIG_MFD_MAX8997[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
help
This option enables device driver support for the haptic controller
on MAXIM MAX8997 chip. This driver supports ff-memless interface
from input framework.
To compile this driver as module, choose [31mCONFIG_M[0m here: the
module will be called max8997-haptic.
config [31mCONFIG_INPUT_MC13783_PWRBUTTON[0m
tristate "MC13783 ON buttons"
depends on [31mCONFIG_MFD_MC13XXX[0m
help
Support the ON buttons of MC13783 PMIC as an input device
reporting power button status.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called mc13783-pwrbutton.
config [31mCONFIG_INPUT_MMA8450[0m
tristate "MMA8450 - Freescale's 3-Axis, 8/12-bit Digital Accelerometer"
depends on [31mCONFIG_I2C[0m
select [31mCONFIG_INPUT_POLLDEV[0m
help
Say Y here if you want to support Freescale's MMA8450 Accelerometer
through [31mCONFIG_I2C[0m interface.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called mma8450.
config [31mCONFIG_INPUT_MPU3050[0m
tristate "MPU3050 Triaxial gyroscope sensor"
depends on [31mCONFIG_I2C[0m
help
Say Y here if you want to support InvenSense [31mCONFIG_MPU3050[0m
connected via an [31mCONFIG_I2C[0m bus.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called mpu3050.
config [31mCONFIG_INPUT_APANEL[0m
tristate "Fujitsu Lifebook Application Panel buttons"
depends on [31mCONFIG_X86[0m && [31mCONFIG_I2C[0m && [31mCONFIG_LEDS_CLASS[0m
select [31mCONFIG_INPUT_POLLDEV[0m
select [31mCONFIG_CHECK_SIGNATURE[0m
help
Say Y here for support of the Application Panel buttons, used on
Fujitsu Lifebook. These are attached to the mainboard through
an SMBus interface managed by the [31mCONFIG_I2C[0m Intel ICH (i801) driver,
which you should also build for this kernel.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will
be called apanel.
config [31mCONFIG_INPUT_GP2A[0m
tristate "Sharp GP2AP002A00F I2C Proximity/Opto sensor driver"
depends on [31mCONFIG_I2C[0m
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
help
Say Y here if you have a Sharp GP2AP002A00F proximity/als combo-chip
hooked to an [31mCONFIG_I2C[0m bus.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called gp2ap002a00f.
config [31mCONFIG_INPUT_GPIO_BEEPER[0m
tristate "Generic GPIO Beeper support"
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
help
Say Y here if you have a beeper connected to a GPIO pin.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called gpio-beeper.
config [31mCONFIG_INPUT_GPIO_TILT_POLLED[0m
tristate "Polled GPIO tilt switch"
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
select [31mCONFIG_INPUT_POLLDEV[0m
help
This driver implements support for tilt switches connected
to GPIO pins that are not capable of generating interrupts.
The list of gpios to use and the mapping of their states
to specific angles is done via platform data.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called gpio_tilt_polled.
config [31mCONFIG_INPUT_GPIO_DECODER[0m
tristate "Polled GPIO Decoder Input driver"
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
select [31mCONFIG_INPUT_POLLDEV[0m
help
Say Y here if you want driver to read status of multiple GPIO
lines and report the encoded value as an absolute integer to
input subsystem.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called gpio_decoder.
config [31mCONFIG_INPUT_IXP4XX_BEEPER[0m
tristate "IXP4XX Beeper support"
depends on [31mCONFIG_ARCH_IXP4XX[0m
help
If you say yes here, you can connect a beeper to the
ixp4xx gpio pins. This is used by the LinkSys NSLU2.
If unsure, say Y.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ixp4xx-beeper.
config [31mCONFIG_INPUT_COBALT_BTNS[0m
tristate "Cobalt button interface"
depends on [31mCONFIG_MIPS_COBALT[0m
select [31mCONFIG_INPUT_POLLDEV[0m
help
Say Y here if you want to support [31mCONFIG_MIPS[0m Cobalt button interface.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called cobalt_btns.
config [31mCONFIG_INPUT_WISTRON_BTNS[0m
tristate "x86 Wistron laptop button interface"
depends on [31mCONFIG_X86_32[0m
select [31mCONFIG_INPUT_POLLDEV[0m
select [31mCONFIG_INPUT_SPARSEKMAP[0m
select [31mCONFIG_NEW_LEDS[0m
select [31mCONFIG_LEDS_CLASS[0m
select [31mCONFIG_CHECK_SIGNATURE[0m
help
Say Y here for support of Wistron laptop button interfaces, used on
laptops of various brands, including Acer and Fujitsu-Siemens. If
available, mail and wifi LEDs will be controllable via /sys/class/leds.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will
be called wistron_btns.
config [31mCONFIG_INPUT_ATLAS_BTNS[0m
tristate "x86 Atlas button interface"
depends on [31mCONFIG_X86[0m && [31mCONFIG_ACPI[0m
help
Say Y here for support of Atlas wallmount touchscreen buttons.
The events will show up as scancodes [31mCONFIG_F1[0m through F9 via evdev.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will
be called atlas_btns.
config [31mCONFIG_INPUT_ATI_REMOTE2[0m
tristate "ATI / Philips USB RF remote control"
depends on [31mCONFIG_USB_ARCH_HAS_HCD[0m
select [31mCONFIG_USB[0m
help
Say Y here if you want to use an ATI or Philips [31mCONFIG_USB[0m RF remote control.
These are RF remotes with [31mCONFIG_USB[0m receivers.
ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
and is also available as a separate product.
This driver provides mouse pointer, left and right mouse buttons,
and maps all the other remote buttons to keypress events.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will be
called ati_remote2.
config [31mCONFIG_INPUT_KEYSPAN_REMOTE[0m
tristate "Keyspan DMR USB remote control"
depends on [31mCONFIG_USB_ARCH_HAS_HCD[0m
select [31mCONFIG_USB[0m
help
Say Y here if you want to use a Keyspan DMR [31mCONFIG_USB[0m remote control.
Currently only the UIA-11 type of receiver has been tested. The tag
on the receiver that connects to the [31mCONFIG_USB[0m port should have a P/N that
will tell you what type of DMR you have. The UIA-10 type is not
supported at this time. This driver maps all buttons to keypress
events.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will
be called keyspan_remote.
config [31mCONFIG_INPUT_KXTJ9[0m
tristate "Kionix KXTJ9 tri-axis digital accelerometer"
depends on [31mCONFIG_I2C[0m
help
Say Y here to enable support for the Kionix KXTJ9 digital tri-axis
accelerometer.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will
be called kxtj9.
config [31mCONFIG_INPUT_KXTJ9_POLLED_MODE[0m
bool "Enable polling mode support"
depends on [31mCONFIG_INPUT_KXTJ9[0m
select [31mCONFIG_INPUT_POLLDEV[0m
help
Say Y here if you need accelerometer to work in polling mode.
config [31mCONFIG_INPUT_POWERMATE[0m
tristate "Griffin PowerMate and Contour Jog support"
depends on [31mCONFIG_USB_ARCH_HAS_HCD[0m
select [31mCONFIG_USB[0m
help
Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
These are aluminum dials which can measure clockwise and anticlockwise
rotation. The dial also acts as a pushbutton. The base contains an LED
which can be instructed to pulse or to switch to a particular intensity.
You can download userspace tools from
<http://sowerbutts.com/powermate/>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called powermate.
config [31mCONFIG_INPUT_YEALINK[0m
tristate "Yealink usb-p1k voip phone"
depends on [31mCONFIG_USB_ARCH_HAS_HCD[0m
select [31mCONFIG_USB[0m
help
Say Y here if you want to enable keyboard and LCD functions of the
Yealink usb-p1k usb phones. The audio part is enabled by the generic
usb sound driver, so you might want to enable that as well.
For information about how to use these additional functions, see
<file:Documentation/input/yealink.txt>.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will be
called yealink.
config [31mCONFIG_INPUT_CM109[0m
tristate "C-Media CM109 USB I/O Controller"
depends on [31mCONFIG_USB_ARCH_HAS_HCD[0m
select [31mCONFIG_USB[0m
help
Say Y here if you want to enable keyboard and buzzer functions of the
[31mCONFIG_C[0m-Media CM109 usb phones. The audio part is enabled by the generic
usb sound driver, so you might want to enable that as well.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will be
called cm109.
config [31mCONFIG_INPUT_REGULATOR_HAPTIC[0m
tristate "Regulator haptics support"
depends on [31mCONFIG_REGULATOR[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
help
This option enables device driver support for the haptic controlled
by a regulator. This driver supports ff-memless interface
from input framework.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called regulator-haptic.
config [31mCONFIG_INPUT_RETU_PWRBUTTON[0m
tristate "Retu Power button Driver"
depends on [31mCONFIG_MFD_RETU[0m
help
Say Y here if you want to enable power key reporting via the
Retu chips found in Nokia Internet Tablets (770, N800, N810).
To compile this driver as a module, choose [31mCONFIG_M[0m here. The module will
be called retu-pwrbutton.
config [31mCONFIG_INPUT_TPS65218_PWRBUTTON[0m
tristate "TPS65218 Power button driver"
depends on ([31mCONFIG_MFD_TPS65217[0m || [31mCONFIG_MFD_TPS65218[0m)
help
Say Y here if you want to enable power buttong reporting for
TPS65217 and TPS65218 Power Management IC devices.
To compile this driver as a module, choose [31mCONFIG_M[0m here. The module will
be called tps65218-pwrbutton.
config [31mCONFIG_INPUT_AXP20X_PEK[0m
tristate "X-Powers AXP20X power button driver"
depends on [31mCONFIG_MFD_AXP20X[0m
help
Say Y here if you want to enable power key reporting via the
AXP20X PMIC.
To compile this driver as a module, choose [31mCONFIG_M[0m here. The module will
be called axp20x-pek.
config [31mCONFIG_INPUT_TWL4030_PWRBUTTON[0m
tristate "TWL4030 Power button Driver"
depends on [31mCONFIG_TWL4030_CORE[0m
help
Say Y here if you want to enable power key reporting via the
TWL4030 family of chips.
To compile this driver as a module, choose [31mCONFIG_M[0m here. The module will
be called twl4030_pwrbutton.
config [31mCONFIG_INPUT_TWL4030_VIBRA[0m
tristate "Support for TWL4030 Vibrator"
depends on [31mCONFIG_TWL4030_CORE[0m
select [31mCONFIG_MFD_TWL4030_AUDIO[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
help
This option enables support for TWL4030 Vibrator Driver.
To compile this driver as a module, choose [31mCONFIG_M[0m here. The module will
be called twl4030_vibra.
config [31mCONFIG_INPUT_TWL6040_VIBRA[0m
tristate "Support for TWL6040 Vibrator"
depends on [31mCONFIG_TWL6040_CORE[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
help
This option enables support for TWL6040 Vibrator Driver.
To compile this driver as a module, choose [31mCONFIG_M[0m here. The module will
be called twl6040_vibra.
config [31mCONFIG_INPUT_UINPUT[0m
tristate "User level driver support"
help
Say Y here if you want to support user level drivers for input
subsystem accessible under char device 10:223 - /dev/input/uinput.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called uinput.
config [31mCONFIG_INPUT_SGI_BTNS[0m
tristate "SGI Indy/O2 volume button interface"
depends on [31mCONFIG_SGI_IP22[0m || [31mCONFIG_SGI_IP32[0m
select [31mCONFIG_INPUT_POLLDEV[0m
help
Say Y here if you want to support SGI Indy/O2 volume button interface.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called sgi_btns.
config [31mCONFIG_HP_SDC_RTC[0m
tristate "HP SDC Real Time Clock"
depends on ([31mCONFIG_GSC[0m || [31mCONFIG_HP300[0m) && [31mCONFIG_SERIO[0m
select [31mCONFIG_HP_SDC[0m
help
Say Y here if you want to support the built-in real time clock
of the HP SDC controller.
config [31mCONFIG_INPUT_PALMAS_PWRBUTTON[0m
tristate "Palmas Power button Driver"
depends on [31mCONFIG_MFD_PALMAS[0m
help
Say Y here if you want to enable power key reporting via the
Palmas family of PMICs.
To compile this driver as a module, choose [31mCONFIG_M[0m here. The module will
be called palmas_pwrbutton.
config [31mCONFIG_INPUT_PCF50633_PMU[0m
tristate "PCF50633 PMU events"
depends on [31mCONFIG_MFD_PCF50633[0m
help
Say Y to include support for delivering PMU events via input
layer on NXP PCF50633.
config [31mCONFIG_INPUT_PCF8574[0m
tristate "PCF8574 Keypad input device"
depends on [31mCONFIG_I2C[0m
help
Say Y here if you want to support a keypad connected via [31mCONFIG_I2C[0m
with a PCF8574.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called pcf8574_keypad.
config [31mCONFIG_INPUT_PWM_BEEPER[0m
tristate "PWM beeper support"
depends on [31mCONFIG_PWM[0m
help
Say Y here to get support for [31mCONFIG_PWM[0m based beeper devices.
If unsure, say N.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will be
called pwm-beeper.
config [31mCONFIG_INPUT_GPIO_ROTARY_ENCODER[0m
tristate "Rotary encoders connected to GPIO pins"
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
help
Say Y here to add support for rotary encoders connected to GPIO lines.
Check file:Documentation/input/rotary-encoder.txt for more
information.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called rotary_encoder.
config [31mCONFIG_INPUT_RB532_BUTTON[0m
tristate "Mikrotik Routerboard 532 button interface"
depends on [31mCONFIG_MIKROTIK_RB532[0m
depends on [31mCONFIG_GPIOLIB[0m
select [31mCONFIG_INPUT_POLLDEV[0m
help
Say Y here if you want support for the S1 button built into
Mikrotik's Routerboard 532.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called rb532_button.
config [31mCONFIG_INPUT_DA9052_ONKEY[0m
tristate "Dialog DA9052/DA9053 Onkey"
depends on [31mCONFIG_PMIC_DA9052[0m
help
Support the ONKEY of Dialog DA9052 PMICs as an input device
reporting power button status.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called da9052_onkey.
config [31mCONFIG_INPUT_DA9055_ONKEY[0m
tristate "Dialog Semiconductor DA9055 ONKEY"
depends on [31mCONFIG_MFD_DA9055[0m
help
Support the ONKEY of DA9055 PMICs as an input device
reporting power button status.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called da9055_onkey.
config [31mCONFIG_INPUT_DA9063_ONKEY[0m
tristate "Dialog DA9063/62/61 OnKey"
depends on [31mCONFIG_MFD_DA9063[0m || [31mCONFIG_MFD_DA9062[0m
help
Support the ONKEY of Dialog DA9063, DA9062 and DA9061 Power
Management ICs as an input device capable of reporting the
power button status.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called da9063_onkey.
config [31mCONFIG_INPUT_DM355EVM[0m
tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
depends on [31mCONFIG_MFD_DM355EVM_MSP[0m
select [31mCONFIG_INPUT_SPARSEKMAP[0m
help
Supports the pushbuttons and IR remote used with
the DM355 [31mCONFIG_EVM[0m board.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called dm355evm_keys.
config [31mCONFIG_INPUT_BFIN_ROTARY[0m
tristate "Blackfin Rotary support"
depends on [31mCONFIG_BF54x[0m || [31mCONFIG_BF52x[0m
help
Say Y here if you want to use the Blackfin Rotary.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called bfin-rotary.
config [31mCONFIG_INPUT_WM831X_ON[0m
tristate "WM831X ON pin"
depends on [31mCONFIG_MFD_WM831X[0m
help
Support the ON pin of WM831X PMICs as an input device
reporting power button status.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module
will be called wm831x_on.
config [31mCONFIG_INPUT_PCAP[0m
tristate "Motorola EZX PCAP misc input events"
depends on [31mCONFIG_EZX_PCAP[0m
help
Say Y here if you want to use Power key and Headphone button
on Motorola EZX phones.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called pcap_keys.
config [31mCONFIG_INPUT_ADXL34X[0m
tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
default n
help
Say Y here if you have a Accelerometer interface using the
[31mCONFIG_ADXL345[0m/6 controller, and your board-specific initialization
code includes that in its table of devices.
This driver can use either [31mCONFIG_I2C[0m or [31mCONFIG_SPI[0m communication to the
[31mCONFIG_ADXL345[0m/6 controller. Select the appropriate method for
your system.
If unsure, say N (but it's safe to say "Y").
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called adxl34x.
config [31mCONFIG_INPUT_ADXL34X_I2C[0m
tristate "support I2C bus connection"
depends on [31mCONFIG_INPUT_ADXL34X[0m && [31mCONFIG_I2C[0m
default y
help
Say Y here if you have [31mCONFIG_ADXL345[0m/6 hooked to an [31mCONFIG_I2C[0m bus.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called adxl34x-i2c.
config [31mCONFIG_INPUT_ADXL34X_SPI[0m
tristate "support SPI bus connection"
depends on [31mCONFIG_INPUT_ADXL34X[0m && [31mCONFIG_SPI[0m
default y
help
Say Y here if you have [31mCONFIG_ADXL345[0m/6 hooked to a [31mCONFIG_SPI[0m bus.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called adxl34x-spi.
config [31mCONFIG_INPUT_IMS_PCU[0m
tristate "IMS Passenger Control Unit driver"
depends on [31mCONFIG_USB[0m
depends on [31mCONFIG_LEDS_CLASS[0m
help
Say Y here if you have system with IMS Rave Passenger Control Unit.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the module will be
called ims_pcu.
config [31mCONFIG_INPUT_CMA3000[0m
tristate "VTI CMA3000 Tri-axis accelerometer"
help
Say Y here if you want to use VTI CMA3000_D0x Accelerometer
driver
This driver currently only supports [31mCONFIG_I2C[0m interface to the
controller. Also select the [31mCONFIG_I2C[0m method.
If unsure, say N
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called cma3000_d0x.
config [31mCONFIG_INPUT_CMA3000_I2C[0m
tristate "Support I2C bus connection"
depends on [31mCONFIG_INPUT_CMA3000[0m && [31mCONFIG_I2C[0m
help
Say Y here if you want to use VTI CMA3000_D0x Accelerometer
through [31mCONFIG_I2C[0m interface.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called cma3000_d0x_i2c.
config [31mCONFIG_INPUT_XEN_KBDDEV_FRONTEND[0m
tristate "Xen virtual keyboard and mouse support"
depends on [31mCONFIG_XEN[0m
default y
select [31mCONFIG_XEN_XENBUS_FRONTEND[0m
help
This driver implements the front-end of the Xen virtual
keyboard and mouse device driver. It communicates with a back-end
in another domain.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called xen-kbdfront.
config [31mCONFIG_INPUT_SIRFSOC_ONKEY[0m
tristate "CSR SiRFSoC power on/off/suspend key support"
depends on [31mCONFIG_ARCH_SIRF[0m && [31mCONFIG_OF[0m
default y
help
Say Y here if you want to support for the SiRFSoC power on/off/suspend key
in Linux, after you press the onkey, system will suspend.
If unsure, say N.
config [31mCONFIG_INPUT_IDEAPAD_SLIDEBAR[0m
tristate "IdeaPad Laptop Slidebar"
depends on [31mCONFIG_INPUT[0m
depends on [31mCONFIG_SERIO_I8042[0m
help
Say Y here if you have an IdeaPad laptop with a slidebar.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called ideapad_slidebar.
config [31mCONFIG_INPUT_SOC_BUTTON_ARRAY[0m
tristate "Windows-compatible SoC Button Array"
depends on [31mCONFIG_KEYBOARD_GPIO[0m
help
Say Y here if you have a SoC-based tablet that originally
runs Windows 8.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called soc_button_array.
config [31mCONFIG_INPUT_DRV260X_HAPTICS[0m
tristate "TI DRV260X haptics support"
depends on [31mCONFIG_INPUT[0m && [31mCONFIG_I2C[0m
depends on [31mCONFIG_GPIOLIB[0m || [31mCONFIG_COMPILE_TEST[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
select [31mCONFIG_REGMAP_I2C[0m
help
Say Y to enable support for the TI DRV260X haptics driver.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called drv260x-haptics.
config [31mCONFIG_INPUT_DRV2665_HAPTICS[0m
tristate "TI DRV2665 haptics support"
depends on [31mCONFIG_INPUT[0m && [31mCONFIG_I2C[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
select [31mCONFIG_REGMAP_I2C[0m
help
Say Y to enable support for the TI DRV2665 haptics driver.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called drv2665-haptics.
config [31mCONFIG_INPUT_DRV2667_HAPTICS[0m
tristate "TI DRV2667 haptics support"
depends on [31mCONFIG_INPUT[0m && [31mCONFIG_I2C[0m
select [31mCONFIG_INPUT_FF_MEMLESS[0m
select [31mCONFIG_REGMAP_I2C[0m
help
Say Y to enable support for the TI DRV2667 haptics driver.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called drv2667-haptics.
config [31mCONFIG_INPUT_HISI_POWERKEY[0m
tristate "Hisilicon PMIC ONKEY support"
depends on [31mCONFIG_ARCH_HISI[0m || [31mCONFIG_COMPILE_TEST[0m
help
Say Y to enable support for PMIC ONKEY.
To compile this driver as a module, choose [31mCONFIG_M[0m here: the
module will be called hisi_powerkey.
endif