[mirror_ubuntu-bionic-kernel.git] / drivers / input / misc / Kconfig

#
# Input misc drivers configuration
#
menuconfig INPUT_MISC
	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 INPUT_MISC

config INPUT_88PM860X_ONKEY
	tristate "88PM860x ONKEY support"
	depends on MFD_88PM860X
	help
	  Support the ONKEY of Marvell 88PM860x PMICs as an input device
	  reporting power button status.

	  To compile this driver as a module, choose M here: the module
	  will be called 88pm860x_onkey.

config INPUT_AB8500_PONKEY
	tristate "AB8500 Pon (PowerOn) Key"
	depends on AB8500_CORE
	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 M here: the module
	  will be called ab8500-ponkey.

config INPUT_AD714X
	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 M here: the
	  module will be called ad714x.

config INPUT_AD714X_I2C
	tristate "support I2C bus connection"
	depends on INPUT_AD714X && I2C
	default y
	help
	  Say Y here if you have AD7142/AD7147 hooked to an I2C bus.

	  To compile this driver as a module, choose M here: the
	  module will be called ad714x-i2c.

config INPUT_AD714X_SPI
	tristate "support SPI bus connection"
	depends on INPUT_AD714X && SPI
	default y
	help
	  Say Y here if you have AD7142/AD7147 hooked to a SPI bus.

	  To compile this driver as a module, choose M here: the
	  module will be called ad714x-spi.

config INPUT_PCSPKR
	tristate "PC Speaker support"
	depends on PCSPKR_PLATFORM
	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 M here: the
	  module will be called pcspkr.

config INPUT_SPARCSPKR
	tristate "SPARC Speaker support"
	depends on PCI && SPARC64
	help
	  Say Y here if you want the standard Speaker on Sparc PCI systems
	  to be used for bells and whistles.

	  If unsure, say Y.

	  To compile this driver as a module, choose M here: the
	  module will be called sparcspkr.

config INPUT_M68K_BEEP
	tristate "M68k Beeper support"
	depends on M68K

config INPUT_MAX8925_ONKEY
	tristate "MAX8925 ONKEY support"
	depends on MFD_MAX8925
	help
	  Support the ONKEY of MAX8925 PMICs as an input device
	  reporting power button status.

	  To compile this driver as a module, choose M here: the module
	  will be called max8925_onkey.

config INPUT_APANEL
	tristate "Fujitsu Lifebook Application Panel buttons"
	depends on X86 && I2C && LEDS_CLASS
	select INPUT_POLLDEV
	select CHECK_SIGNATURE
	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 I2C Intel ICH (i801) driver,
	 which you should also build for this kernel.

	 To compile this driver as a module, choose M here: the module will
	 be called apanel.

config INPUT_IXP4XX_BEEPER
	tristate "IXP4XX Beeper support"
	depends on ARCH_IXP4XX
	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 M here: the
	  module will be called ixp4xx-beeper.

config INPUT_COBALT_BTNS
	tristate "Cobalt button interface"
	depends on MIPS_COBALT
	select INPUT_POLLDEV
	help
	  Say Y here if you want to support MIPS Cobalt button interface.

	  To compile this driver as a module, choose M here: the
	  module will be called cobalt_btns.

config INPUT_WISTRON_BTNS
	tristate "x86 Wistron laptop button interface"
	depends on X86 && !X86_64
	select INPUT_POLLDEV
	select INPUT_SPARSEKMAP
	select NEW_LEDS
	select LEDS_CLASS
	select CHECK_SIGNATURE
	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 M here: the module will
	  be called wistron_btns.

config INPUT_ATLAS_BTNS
	tristate "x86 Atlas button interface"
	depends on X86 && ACPI
	help
	  Say Y here for support of Atlas wallmount touchscreen buttons.
	  The events will show up as scancodes F1 through F9 via evdev.

	  To compile this driver as a module, choose M here: the module will
	  be called atlas_btns.

config INPUT_ATI_REMOTE
	tristate "ATI / X10 USB RF remote control"
	depends on USB_ARCH_HAS_HCD
	select USB
	help
	  Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
	  These are RF remotes with USB receivers.
	  The ATI remote comes with many of ATI's All-In-Wonder video cards.
	  The X10 "Lola" remote is available at:
	     <http://www.x10.com/products/lola_sg1.htm>
	  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 M here: the module will be
	  called ati_remote.

config INPUT_ATI_REMOTE2
	tristate "ATI / Philips USB RF remote control"
	depends on USB_ARCH_HAS_HCD
	select USB
	help
	  Say Y here if you want to use an ATI or Philips USB RF remote control.
	  These are RF remotes with USB 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 M here: the module will be
	  called ati_remote2.

config INPUT_KEYSPAN_REMOTE
	tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
	depends on EXPERIMENTAL
	depends on USB_ARCH_HAS_HCD
	select USB
	help
	  Say Y here if you want to use a Keyspan DMR USB remote control.
	  Currently only the UIA-11 type of receiver has been tested.  The tag
	  on the receiver that connects to the USB 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 M here: the module will
	  be called keyspan_remote.

config INPUT_POWERMATE
	tristate "Griffin PowerMate and Contour Jog support"
	depends on USB_ARCH_HAS_HCD
	select USB
	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 M here: the
	  module will be called powermate.

config INPUT_YEALINK
	tristate "Yealink usb-p1k voip phone"
	depends on EXPERIMENTAL
	depends on USB_ARCH_HAS_HCD
	select USB
	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 M here: the module will be
	  called yealink.

config INPUT_CM109
	tristate "C-Media CM109 USB I/O Controller"
	depends on EXPERIMENTAL
	depends on USB_ARCH_HAS_HCD
	select USB
	help
	  Say Y here if you want to enable keyboard and buzzer functions of the
	  C-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 M here: the module will be
	  called cm109.

config INPUT_TWL4030_PWRBUTTON
	tristate "TWL4030 Power button Driver"
	depends on TWL4030_CORE
	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 M here. The module will
	  be called twl4030_pwrbutton.

config INPUT_TWL4030_VIBRA
	tristate "Support for TWL4030 Vibrator"
	depends on TWL4030_CORE
	select TWL4030_CODEC
	select INPUT_FF_MEMLESS
	help
	  This option enables support for TWL4030 Vibrator Driver.

	  To compile this driver as a module, choose M here. The module will
	  be called twl4030_vibra.

config INPUT_UINPUT
	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 M here: the
	  module will be called uinput.

config INPUT_SGI_BTNS
	tristate "SGI Indy/O2 volume button interface"
	depends on SGI_IP22 || SGI_IP32
	select INPUT_POLLDEV
	help
	  Say Y here if you want to support SGI Indy/O2 volume button interface.

	  To compile this driver as a module, choose M here: the
	  module will be called sgi_btns.

config HP_SDC_RTC
	tristate "HP SDC Real Time Clock"
	depends on (GSC || HP300) && SERIO
	select HP_SDC
	help
	  Say Y here if you want to support the built-in real time clock
	  of the HP SDC controller.

config INPUT_PCF50633_PMU
	tristate "PCF50633 PMU events"
	depends on MFD_PCF50633
	help
	 Say Y to include support for delivering  PMU events via  input
	 layer on NXP PCF50633.

config INPUT_PCF8574
	tristate "PCF8574 Keypad input device"
	depends on I2C && EXPERIMENTAL
	help
	  Say Y here if you want to support a keypad connetced via I2C
	  with a PCF8574.

	  To compile this driver as a module, choose M here: the
	  module will be called pcf8574_keypad.

config INPUT_PWM_BEEPER
	tristate "PWM beeper support"
	depends on HAVE_PWM
	help
	  Say Y here to get support for PWM based beeper devices.

	  If unsure, say N.

	  To compile this driver as a module, choose M here: the module will be
	  called pwm-beeper.

config INPUT_PMIC8XXX_PWRKEY
	tristate "PMIC8XXX power key support"
	depends on MFD_PM8XXX
	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 M here: the
	  module will be called pmic8xxx-pwrkey.

config INPUT_GPIO_ROTARY_ENCODER
	tristate "Rotary encoders connected to GPIO pins"
	depends on GPIOLIB && GENERIC_GPIO
	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 M here: the
	  module will be called rotary_encoder.

config INPUT_RB532_BUTTON
	tristate "Mikrotik Routerboard 532 button interface"
	depends on MIKROTIK_RB532
	depends on GPIOLIB && GENERIC_GPIO
	select INPUT_POLLDEV
	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 M here: the
	  module will be called rb532_button.

config INPUT_DM355EVM
	tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
	depends on MFD_DM355EVM_MSP
	select INPUT_SPARSEKMAP
	help
	  Supports the pushbuttons and IR remote used with
	  the DM355 EVM board.

	  To compile this driver as a module, choose M here: the
	  module will be called dm355evm_keys.

config INPUT_BFIN_ROTARY
	tristate "Blackfin Rotary support"
	depends on BF54x || BF52x
	help
	  Say Y here if you want to use the Blackfin Rotary.

	  To compile this driver as a module, choose M here: the
	  module will be called bfin-rotary.

config INPUT_WM831X_ON
	tristate "WM831X ON pin"
	depends on MFD_WM831X
	help
	  Support the ON pin of WM831X PMICs as an input device
	  reporting power button status.

	  To compile this driver as a module, choose M here: the module
	  will be called wm831x_on.

config INPUT_PCAP
	tristate "Motorola EZX PCAP misc input events"
	depends on EZX_PCAP
	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 M here: the
	  module will be called pcap_keys.

config INPUT_ADXL34X
	tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
	default n
	help
	  Say Y here if you have a Accelerometer interface using the
	  ADXL345/6 controller, and your board-specific initialization
	  code includes that in its table of devices.

	  This driver can use either I2C or SPI communication to the
	  ADXL345/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 M here: the
	  module will be called adxl34x.

config INPUT_ADXL34X_I2C
	tristate "support I2C bus connection"
	depends on INPUT_ADXL34X && I2C
	default y
	help
	  Say Y here if you have ADXL345/6 hooked to an I2C bus.

	  To compile this driver as a module, choose M here: the
	  module will be called adxl34x-i2c.

config INPUT_ADXL34X_SPI
	tristate "support SPI bus connection"
	depends on INPUT_ADXL34X && SPI
	default y
	help
	  Say Y here if you have ADXL345/6 hooked to a SPI bus.

	  To compile this driver as a module, choose M here: the
	  module will be called adxl34x-spi.

config INPUT_CMA3000
	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 I2C interface to the
	  controller. Also select the I2C method.

	  If unsure, say N

	  To compile this driver as a module, choose M here: the
	  module will be called cma3000_d0x.

config INPUT_CMA3000_I2C
	tristate "Support I2C bus connection"
	depends on INPUT_CMA3000 && I2C
	help
	  Say Y here if you want to use VTI CMA3000_D0x Accelerometer
	  through I2C interface.

	  To compile this driver as a module, choose M here: the
	  module will be called cma3000_d0x_i2c.

config INPUT_XEN_KBDDEV_FRONTEND
	tristate "Xen virtual keyboard and mouse support"
	depends on XEN_FBDEV_FRONTEND
	default y
	select XEN_XENBUS_FRONTEND
	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 M here: the
	  module will be called xen-kbdfront.

endif
Commit	Line	Data
1da177e4 LT	1	#
	2	# Input misc drivers configuration
	3	#
	4	menuconfig INPUT_MISC
	5	bool "Miscellaneous devices"
	6	help
	7	Say Y here, and a list of miscellaneous input drivers will be displayed.
	8	Everything that didn't fit into the other categories is here. This option
	9	doesn't affect the kernel.
	10
	11	If unsure, say Y.
	12
	13	if INPUT_MISC
	14
69854031 HZ	15	config INPUT_88PM860X_ONKEY
	16	tristate "88PM860x ONKEY support"
	17	depends on MFD_88PM860X
	18	help
	19	Support the ONKEY of Marvell 88PM860x PMICs as an input device
	20	reporting power button status.
	21
	22	To compile this driver as a module, choose M here: the module
	23	will be called 88pm860x_onkey.
	24
77686517 SI	25	config INPUT_AB8500_PONKEY
	26	tristate "AB8500 Pon (PowerOn) Key"
	27	depends on AB8500_CORE
	28	help
	29	Say Y here to use the PowerOn Key for ST-Ericsson's AB8500
	30	Mix-Sig PMIC.
	31
	32	To compile this driver as a module, choose M here: the module
	33	will be called ab8500-ponkey.
	34
31a62963 BW	35	config INPUT_AD714X
	36	tristate "Analog Devices AD714x Capacitance Touch Sensor"
	37	help
6c04d7b3	38	Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
31a62963 BW	39
	40	You should select a bus connection too.
	41
	42	To compile this driver as a module, choose M here: the
	43	module will be called ad714x.
	44
	45	config INPUT_AD714X_I2C
	46	tristate "support I2C bus connection"
	47	depends on INPUT_AD714X && I2C
	48	default y
	49	help
	50	Say Y here if you have AD7142/AD7147 hooked to an I2C bus.
	51
	52	To compile this driver as a module, choose M here: the
	53	module will be called ad714x-i2c.
	54
	55	config INPUT_AD714X_SPI
	56	tristate "support SPI bus connection"
	57	depends on INPUT_AD714X && SPI
	58	default y
	59	help
	60	Say Y here if you have AD7142/AD7147 hooked to a SPI bus.
	61
	62	To compile this driver as a module, choose M here: the
	63	module will be called ad714x-spi.
	64
1da177e4 LT	65	config INPUT_PCSPKR
1da177e4 LT	66	tristate "PC Speaker support"
e5e1d3cb	67	depends on PCSPKR_PLATFORM
1da177e4 LT	68	help
	69	Say Y here if you want the standard PC Speaker to be used for
	70	bells and whistles.
	71
	72	If unsure, say Y.
	73
	74	To compile this driver as a module, choose M here: the
	75	module will be called pcspkr.
	76
	77	config INPUT_SPARCSPKR
	78	tristate "SPARC Speaker support"
a2bd4fd1	79	depends on PCI && SPARC64
1da177e4 LT	80	help
	81	Say Y here if you want the standard Speaker on Sparc PCI systems
	82	to be used for bells and whistles.
	83
	84	If unsure, say Y.
	85
	86	To compile this driver as a module, choose M here: the
	87	module will be called sparcspkr.
	88
	89	config INPUT_M68K_BEEP
	90	tristate "M68k Beeper support"
	91	depends on M68K
	92
3734574c HZ	93	config INPUT_MAX8925_ONKEY
	94	tristate "MAX8925 ONKEY support"
	95	depends on MFD_MAX8925
	96	help
	97	Support the ONKEY of MAX8925 PMICs as an input device
	98	reporting power button status.
	99
	100	To compile this driver as a module, choose M here: the module
	101	will be called max8925_onkey.
	102
52fe0cdb SH	103	config INPUT_APANEL
52fe0cdb SH	104	tristate "Fujitsu Lifebook Application Panel buttons"
19131305	105	depends on X86 && I2C && LEDS_CLASS
52fe0cdb SH	106	select INPUT_POLLDEV
	107	select CHECK_SIGNATURE
	108	help
	109	Say Y here for support of the Application Panel buttons, used on
	110	Fujitsu Lifebook. These are attached to the mainboard through
19131305 RD	111	an SMBus interface managed by the I2C Intel ICH (i801) driver,
19131305 RD	112	which you should also build for this kernel.
52fe0cdb SH	113
	114	To compile this driver as a module, choose M here: the module will
	115	be called apanel.
	116
ba0acb5e DT	117	config INPUT_IXP4XX_BEEPER
	118	tristate "IXP4XX Beeper support"
	119	depends on ARCH_IXP4XX
	120	help
	121	If you say yes here, you can connect a beeper to the
	122	ixp4xx gpio pins. This is used by the LinkSys NSLU2.
	123
	124	If unsure, say Y.
	125
	126	To compile this driver as a module, choose M here: the
	127	module will be called ixp4xx-beeper.
	128
bebb8a2b YY	129	config INPUT_COBALT_BTNS
	130	tristate "Cobalt button interface"
	131	depends on MIPS_COBALT
3d29cdff	132	select INPUT_POLLDEV
bebb8a2b YY	133	help
	134	Say Y here if you want to support MIPS Cobalt button interface.
	135
	136	To compile this driver as a module, choose M here: the
	137	module will be called cobalt_btns.
	138
5fc14680 DT	139	config INPUT_WISTRON_BTNS
5fc14680 DT	140	tristate "x86 Wistron laptop button interface"
e9fb028e	141	depends on X86 && !X86_64
c2554c91	142	select INPUT_POLLDEV
e97af4cb	143	select INPUT_SPARSEKMAP
389679d8 EP	144	select NEW_LEDS
389679d8 EP	145	select LEDS_CLASS
928923c7	146	select CHECK_SIGNATURE
5fc14680	147	help
01dd2fbf	148	Say Y here for support of Wistron laptop button interfaces, used on
389679d8	149	laptops of various brands, including Acer and Fujitsu-Siemens. If
01dd2fbf	150	available, mail and wifi LEDs will be controllable via /sys/class/leds.
5fc14680 DT	151
	152	To compile this driver as a module, choose M here: the module will
	153	be called wistron_btns.
	154
31ea7ff0 JK	155	config INPUT_ATLAS_BTNS
	156	tristate "x86 Atlas button interface"
	157	depends on X86 && ACPI
	158	help
	159	Say Y here for support of Atlas wallmount touchscreen buttons.
	160	The events will show up as scancodes F1 through F9 via evdev.
	161
	162	To compile this driver as a module, choose M here: the module will
	163	be called atlas_btns.
	164
ba0acb5e DT	165	config INPUT_ATI_REMOTE
ba0acb5e DT	166	tristate "ATI / X10 USB RF remote control"
7a86edef	167	depends on USB_ARCH_HAS_HCD
ba0acb5e	168	select USB
01387959	169	help
ba0acb5e DT	170	Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
	171	These are RF remotes with USB receivers.
	172	The ATI remote comes with many of ATI's All-In-Wonder video cards.
	173	The X10 "Lola" remote is available at:
	174	<http://www.x10.com/products/lola_sg1.htm>
	175	This driver provides mouse pointer, left and right mouse buttons,
	176	and maps all the other remote buttons to keypress events.
	177
	178	To compile this driver as a module, choose M here: the module will be
	179	called ati_remote.
	180
	181	config INPUT_ATI_REMOTE2
	182	tristate "ATI / Philips USB RF remote control"
7a86edef	183	depends on USB_ARCH_HAS_HCD
ba0acb5e DT	184	select USB
	185	help
	186	Say Y here if you want to use an ATI or Philips USB RF remote control.
	187	These are RF remotes with USB receivers.
	188	ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
	189	and is also available as a separate product.
	190	This driver provides mouse pointer, left and right mouse buttons,
	191	and maps all the other remote buttons to keypress events.
	192
	193	To compile this driver as a module, choose M here: the module will be
	194	called ati_remote2.
	195
	196	config INPUT_KEYSPAN_REMOTE
	197	tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
	198	depends on EXPERIMENTAL
7a86edef	199	depends on USB_ARCH_HAS_HCD
ba0acb5e DT	200	select USB
	201	help
	202	Say Y here if you want to use a Keyspan DMR USB remote control.
	203	Currently only the UIA-11 type of receiver has been tested. The tag
	204	on the receiver that connects to the USB port should have a P/N that
	205	will tell you what type of DMR you have. The UIA-10 type is not
	206	supported at this time. This driver maps all buttons to keypress
	207	events.
01387959	208
ba0acb5e DT	209	To compile this driver as a module, choose M here: the module will
	210	be called keyspan_remote.
	211
	212	config INPUT_POWERMATE
	213	tristate "Griffin PowerMate and Contour Jog support"
7a86edef	214	depends on USB_ARCH_HAS_HCD
ba0acb5e DT	215	select USB
	216	help
	217	Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
	218	These are aluminum dials which can measure clockwise and anticlockwise
	219	rotation. The dial also acts as a pushbutton. The base contains an LED
	220	which can be instructed to pulse or to switch to a particular intensity.
	221
	222	You can download userspace tools from
	223	<http://sowerbutts.com/powermate/>.
01387959 AZ	224
01387959 AZ	225	To compile this driver as a module, choose M here: the
ba0acb5e DT	226	module will be called powermate.
	227
	228	config INPUT_YEALINK
	229	tristate "Yealink usb-p1k voip phone"
247537b9	230	depends on EXPERIMENTAL
7a86edef	231	depends on USB_ARCH_HAS_HCD
ba0acb5e DT	232	select USB
	233	help
	234	Say Y here if you want to enable keyboard and LCD functions of the
	235	Yealink usb-p1k usb phones. The audio part is enabled by the generic
	236	usb sound driver, so you might want to enable that as well.
	237
	238	For information about how to use these additional functions, see
	239	<file:Documentation/input/yealink.txt>.
	240
	241	To compile this driver as a module, choose M here: the module will be
	242	called yealink.
01387959	243
c04148f9 AH	244	config INPUT_CM109
	245	tristate "C-Media CM109 USB I/O Controller"
	246	depends on EXPERIMENTAL
	247	depends on USB_ARCH_HAS_HCD
	248	select USB
	249	help
	250	Say Y here if you want to enable keyboard and buzzer functions of the
	251	C-Media CM109 usb phones. The audio part is enabled by the generic
	252	usb sound driver, so you might want to enable that as well.
	253
	254	To compile this driver as a module, choose M here: the module will be
	255	called cm109.
	256
68d8bf04 FB	257	config INPUT_TWL4030_PWRBUTTON
	258	tristate "TWL4030 Power button Driver"
	259	depends on TWL4030_CORE
	260	help
	261	Say Y here if you want to enable power key reporting via the
	262	TWL4030 family of chips.
	263
	264	To compile this driver as a module, choose M here. The module will
	265	be called twl4030_pwrbutton.
	266
3dd1b394 JV	267	config INPUT_TWL4030_VIBRA
	268	tristate "Support for TWL4030 Vibrator"
	269	depends on TWL4030_CORE
	270	select TWL4030_CODEC
	271	select INPUT_FF_MEMLESS
	272	help
	273	This option enables support for TWL4030 Vibrator Driver.
	274
	275	To compile this driver as a module, choose M here. The module will
	276	be called twl4030_vibra.
	277
1da177e4 LT	278	config INPUT_UINPUT
	279	tristate "User level driver support"
	280	help
	281	Say Y here if you want to support user level drivers for input
	282	subsystem accessible under char device 10:223 - /dev/input/uinput.
	283
	284	To compile this driver as a module, choose M here: the
	285	module will be called uinput.
	286
48ad88b1 TB	287	config INPUT_SGI_BTNS
	288	tristate "SGI Indy/O2 volume button interface"
	289	depends on SGI_IP22 \|\| SGI_IP32
3bee2a04 TB	290	select INPUT_POLLDEV
3bee2a04 TB	291	help
48ad88b1	292	Say Y here if you want to support SGI Indy/O2 volume button interface.
3bee2a04 TB	293
3bee2a04 TB	294	To compile this driver as a module, choose M here: the
48ad88b1	295	module will be called sgi_btns.
3bee2a04	296
1da177e4	297	config HP_SDC_RTC
bebb8a2b	298	tristate "HP SDC Real Time Clock"
d061ebd5	299	depends on (GSC \|\| HP300) && SERIO
1da177e4 LT	300	select HP_SDC
	301	help
	302	Say Y here if you want to support the built-in real time clock
	303	of the HP SDC controller.
	304
1851b06a BR	305	config INPUT_PCF50633_PMU
	306	tristate "PCF50633 PMU events"
	307	depends on MFD_PCF50633
	308	help
	309	Say Y to include support for delivering PMU events via input
	310	layer on NXP PCF50633.
	311
b91c4be7 BW	312	config INPUT_PCF8574
	313	tristate "PCF8574 Keypad input device"
	314	depends on I2C && EXPERIMENTAL
	315	help
	316	Say Y here if you want to support a keypad connetced via I2C
	317	with a PCF8574.
	318
	319	To compile this driver as a module, choose M here: the
	320	module will be called pcf8574_keypad.
	321
e22739d0 LPC	322	config INPUT_PWM_BEEPER
	323	tristate "PWM beeper support"
	324	depends on HAVE_PWM
	325	help
	326	Say Y here to get support for PWM based beeper devices.
	327
	328	If unsure, say N.
	329
	330	To compile this driver as a module, choose M here: the module will be
	331	called pwm-beeper.
	332
92d57a73 TS	333	config INPUT_PMIC8XXX_PWRKEY
	334	tristate "PMIC8XXX power key support"
	335	depends on MFD_PM8XXX
	336	help
	337	Say Y here if you want support for the PMIC8XXX power key.
	338
	339	If unsure, say N.
	340
	341	To compile this driver as a module, choose M here: the
	342	module will be called pmic8xxx-pwrkey.
	343
73969ff0 DM	344	config INPUT_GPIO_ROTARY_ENCODER
	345	tristate "Rotary encoders connected to GPIO pins"
	346	depends on GPIOLIB && GENERIC_GPIO
	347	help
	348	Say Y here to add support for rotary encoders connected to GPIO lines.
492d0f95	349	Check file:Documentation/input/rotary-encoder.txt for more
73969ff0 DM	350	information.
	351
	352	To compile this driver as a module, choose M here: the
	353	module will be called rotary_encoder.
	354
d9bdffd2 PS	355	config INPUT_RB532_BUTTON
	356	tristate "Mikrotik Routerboard 532 button interface"
	357	depends on MIKROTIK_RB532
	358	depends on GPIOLIB && GENERIC_GPIO
	359	select INPUT_POLLDEV
	360	help
	361	Say Y here if you want support for the S1 button built into
	362	Mikrotik's Routerboard 532.
	363
	364	To compile this driver as a module, choose M here: the
	365	module will be called rb532_button.
	366
eb990b55 DB	367	config INPUT_DM355EVM
	368	tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
	369	depends on MFD_DM355EVM_MSP
66040727	370	select INPUT_SPARSEKMAP
eb990b55 DB	371	help
	372	Supports the pushbuttons and IR remote used with
	373	the DM355 EVM board.
	374
	375	To compile this driver as a module, choose M here: the
	376	module will be called dm355evm_keys.
48329582 MH	377
	378	config INPUT_BFIN_ROTARY
	379	tristate "Blackfin Rotary support"
	380	depends on BF54x \|\| BF52x
	381	help
	382	Say Y here if you want to use the Blackfin Rotary.
	383
	384	To compile this driver as a module, choose M here: the
	385	module will be called bfin-rotary.
	386
0c73b992 MB	387	config INPUT_WM831X_ON
	388	tristate "WM831X ON pin"
	389	depends on MFD_WM831X
	390	help
	391	Support the ON pin of WM831X PMICs as an input device
	392	reporting power button status.
	393
	394	To compile this driver as a module, choose M here: the module
	395	will be called wm831x_on.
	396
d0a82132 DR	397	config INPUT_PCAP
	398	tristate "Motorola EZX PCAP misc input events"
	399	depends on EZX_PCAP
	400	help
	401	Say Y here if you want to use Power key and Headphone button
	402	on Motorola EZX phones.
	403
	404	To compile this driver as a module, choose M here: the
	405	module will be called pcap_keys.
	406
e27c7292 MH	407	config INPUT_ADXL34X
	408	tristate "Analog Devices ADXL34x Three-Axis Digital Accelerometer"
	409	default n
	410	help
	411	Say Y here if you have a Accelerometer interface using the
	412	ADXL345/6 controller, and your board-specific initialization
	413	code includes that in its table of devices.
	414
	415	This driver can use either I2C or SPI communication to the
	416	ADXL345/6 controller. Select the appropriate method for
	417	your system.
	418
	419	If unsure, say N (but it's safe to say "Y").
	420
	421	To compile this driver as a module, choose M here: the
	422	module will be called adxl34x.
	423
	424	config INPUT_ADXL34X_I2C
	425	tristate "support I2C bus connection"
	426	depends on INPUT_ADXL34X && I2C
	427	default y
	428	help
	429	Say Y here if you have ADXL345/6 hooked to an I2C bus.
	430
	431	To compile this driver as a module, choose M here: the
	432	module will be called adxl34x-i2c.
	433
	434	config INPUT_ADXL34X_SPI
	435	tristate "support SPI bus connection"
	436	depends on INPUT_ADXL34X && SPI
	437	default y
	438	help
	439	Say Y here if you have ADXL345/6 hooked to a SPI bus.
	440
	441	To compile this driver as a module, choose M here: the
	442	module will be called adxl34x-spi.
	443
b029ffaf H	444	config INPUT_CMA3000
	445	tristate "VTI CMA3000 Tri-axis accelerometer"
	446	help
	447	Say Y here if you want to use VTI CMA3000_D0x Accelerometer
	448	driver
	449
	450	This driver currently only supports I2C interface to the
	451	controller. Also select the I2C method.
	452
	453	If unsure, say N
	454
	455	To compile this driver as a module, choose M here: the
	456	module will be called cma3000_d0x.
	457
	458	config INPUT_CMA3000_I2C
	459	tristate "Support I2C bus connection"
	460	depends on INPUT_CMA3000 && I2C
	461	help
	462	Say Y here if you want to use VTI CMA3000_D0x Accelerometer
	463	through I2C interface.
	464
	465	To compile this driver as a module, choose M here: the
	466	module will be called cma3000_d0x_i2c.
	467
49851ca0 DT	468	config INPUT_XEN_KBDDEV_FRONTEND
	469	tristate "Xen virtual keyboard and mouse support"
	470	depends on XEN_FBDEV_FRONTEND
	471	default y
	472	select XEN_XENBUS_FRONTEND
	473	help
	474	This driver implements the front-end of the Xen virtual
	475	keyboard and mouse device driver. It communicates with a back-end
	476	in another domain.
	477
	478	To compile this driver as a module, choose M here: the
	479	module will be called xen-kbdfront.
	480
1da177e4	481	endif