[net-next-2.6.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_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_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 INPUT_WINBOND_CIR
	tristate "Winbond IR remote control"
	depends on X86 && PNP
	select NEW_LEDS
	select LEDS_CLASS
	select LEDS_TRIGGERS
	select BITREVERSE
	help
	  Say Y here if you want to use the IR remote functionality found
	  in some Winbond SuperI/O chips. Currently only the WPCD376I
	  chip is supported (included in some Intel Media series motherboards).

	  IR Receive and wake-on-IR from suspend and power-off is currently
	  supported.

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

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_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.

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
31a62963 BW	25	config INPUT_AD714X
	26	tristate "Analog Devices AD714x Capacitance Touch Sensor"
	27	help
6c04d7b3	28	Say Y here if you want to support an AD7142/3/7/8/7A touch sensor.
31a62963 BW	29
	30	You should select a bus connection too.
	31
	32	To compile this driver as a module, choose M here: the
	33	module will be called ad714x.
	34
	35	config INPUT_AD714X_I2C
	36	tristate "support I2C bus connection"
	37	depends on INPUT_AD714X && I2C
	38	default y
	39	help
	40	Say Y here if you have AD7142/AD7147 hooked to an I2C bus.
	41
	42	To compile this driver as a module, choose M here: the
	43	module will be called ad714x-i2c.
	44
	45	config INPUT_AD714X_SPI
	46	tristate "support SPI bus connection"
	47	depends on INPUT_AD714X && SPI
	48	default y
	49	help
	50	Say Y here if you have AD7142/AD7147 hooked to a SPI bus.
	51
	52	To compile this driver as a module, choose M here: the
	53	module will be called ad714x-spi.
	54
1da177e4 LT	55	config INPUT_PCSPKR
1da177e4 LT	56	tristate "PC Speaker support"
e5e1d3cb	57	depends on PCSPKR_PLATFORM
1da177e4 LT	58	help
	59	Say Y here if you want the standard PC Speaker to be used for
	60	bells and whistles.
	61
	62	If unsure, say Y.
	63
	64	To compile this driver as a module, choose M here: the
	65	module will be called pcspkr.
	66
	67	config INPUT_SPARCSPKR
	68	tristate "SPARC Speaker support"
a2bd4fd1	69	depends on PCI && SPARC64
1da177e4 LT	70	help
	71	Say Y here if you want the standard Speaker on Sparc PCI systems
	72	to be used for bells and whistles.
	73
	74	If unsure, say Y.
	75
	76	To compile this driver as a module, choose M here: the
	77	module will be called sparcspkr.
	78
	79	config INPUT_M68K_BEEP
	80	tristate "M68k Beeper support"
	81	depends on M68K
	82
52fe0cdb SH	83	config INPUT_APANEL
52fe0cdb SH	84	tristate "Fujitsu Lifebook Application Panel buttons"
19131305	85	depends on X86 && I2C && LEDS_CLASS
52fe0cdb SH	86	select INPUT_POLLDEV
	87	select CHECK_SIGNATURE
	88	help
	89	Say Y here for support of the Application Panel buttons, used on
	90	Fujitsu Lifebook. These are attached to the mainboard through
19131305 RD	91	an SMBus interface managed by the I2C Intel ICH (i801) driver,
19131305 RD	92	which you should also build for this kernel.
52fe0cdb SH	93
	94	To compile this driver as a module, choose M here: the module will
	95	be called apanel.
	96
ba0acb5e DT	97	config INPUT_IXP4XX_BEEPER
	98	tristate "IXP4XX Beeper support"
	99	depends on ARCH_IXP4XX
	100	help
	101	If you say yes here, you can connect a beeper to the
	102	ixp4xx gpio pins. This is used by the LinkSys NSLU2.
	103
	104	If unsure, say Y.
	105
	106	To compile this driver as a module, choose M here: the
	107	module will be called ixp4xx-beeper.
	108
bebb8a2b YY	109	config INPUT_COBALT_BTNS
	110	tristate "Cobalt button interface"
	111	depends on MIPS_COBALT
3d29cdff	112	select INPUT_POLLDEV
bebb8a2b YY	113	help
	114	Say Y here if you want to support MIPS Cobalt button interface.
	115
	116	To compile this driver as a module, choose M here: the
	117	module will be called cobalt_btns.
	118
5fc14680 DT	119	config INPUT_WISTRON_BTNS
5fc14680 DT	120	tristate "x86 Wistron laptop button interface"
e9fb028e	121	depends on X86 && !X86_64
c2554c91	122	select INPUT_POLLDEV
e97af4cb	123	select INPUT_SPARSEKMAP
389679d8 EP	124	select NEW_LEDS
389679d8 EP	125	select LEDS_CLASS
928923c7	126	select CHECK_SIGNATURE
5fc14680	127	help
01dd2fbf	128	Say Y here for support of Wistron laptop button interfaces, used on
389679d8	129	laptops of various brands, including Acer and Fujitsu-Siemens. If
01dd2fbf	130	available, mail and wifi LEDs will be controllable via /sys/class/leds.
5fc14680 DT	131
	132	To compile this driver as a module, choose M here: the module will
	133	be called wistron_btns.
	134
31ea7ff0 JK	135	config INPUT_ATLAS_BTNS
	136	tristate "x86 Atlas button interface"
	137	depends on X86 && ACPI
	138	help
	139	Say Y here for support of Atlas wallmount touchscreen buttons.
	140	The events will show up as scancodes F1 through F9 via evdev.
	141
	142	To compile this driver as a module, choose M here: the module will
	143	be called atlas_btns.
	144
ba0acb5e DT	145	config INPUT_ATI_REMOTE
ba0acb5e DT	146	tristate "ATI / X10 USB RF remote control"
7a86edef	147	depends on USB_ARCH_HAS_HCD
ba0acb5e	148	select USB
01387959	149	help
ba0acb5e DT	150	Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
	151	These are RF remotes with USB receivers.
	152	The ATI remote comes with many of ATI's All-In-Wonder video cards.
	153	The X10 "Lola" remote is available at:
	154	<http://www.x10.com/products/lola_sg1.htm>
	155	This driver provides mouse pointer, left and right mouse buttons,
	156	and maps all the other remote buttons to keypress events.
	157
	158	To compile this driver as a module, choose M here: the module will be
	159	called ati_remote.
	160
	161	config INPUT_ATI_REMOTE2
	162	tristate "ATI / Philips USB RF remote control"
7a86edef	163	depends on USB_ARCH_HAS_HCD
ba0acb5e DT	164	select USB
	165	help
	166	Say Y here if you want to use an ATI or Philips USB RF remote control.
	167	These are RF remotes with USB receivers.
	168	ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
	169	and is also available as a separate product.
	170	This driver provides mouse pointer, left and right mouse buttons,
	171	and maps all the other remote buttons to keypress events.
	172
	173	To compile this driver as a module, choose M here: the module will be
	174	called ati_remote2.
	175
	176	config INPUT_KEYSPAN_REMOTE
	177	tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
	178	depends on EXPERIMENTAL
7a86edef	179	depends on USB_ARCH_HAS_HCD
ba0acb5e DT	180	select USB
	181	help
	182	Say Y here if you want to use a Keyspan DMR USB remote control.
	183	Currently only the UIA-11 type of receiver has been tested. The tag
	184	on the receiver that connects to the USB port should have a P/N that
	185	will tell you what type of DMR you have. The UIA-10 type is not
	186	supported at this time. This driver maps all buttons to keypress
	187	events.
01387959	188
ba0acb5e DT	189	To compile this driver as a module, choose M here: the module will
	190	be called keyspan_remote.
	191
	192	config INPUT_POWERMATE
	193	tristate "Griffin PowerMate and Contour Jog support"
7a86edef	194	depends on USB_ARCH_HAS_HCD
ba0acb5e DT	195	select USB
	196	help
	197	Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
	198	These are aluminum dials which can measure clockwise and anticlockwise
	199	rotation. The dial also acts as a pushbutton. The base contains an LED
	200	which can be instructed to pulse or to switch to a particular intensity.
	201
	202	You can download userspace tools from
	203	<http://sowerbutts.com/powermate/>.
01387959 AZ	204
01387959 AZ	205	To compile this driver as a module, choose M here: the
ba0acb5e DT	206	module will be called powermate.
	207
	208	config INPUT_YEALINK
	209	tristate "Yealink usb-p1k voip phone"
247537b9	210	depends on EXPERIMENTAL
7a86edef	211	depends on USB_ARCH_HAS_HCD
ba0acb5e DT	212	select USB
	213	help
	214	Say Y here if you want to enable keyboard and LCD functions of the
	215	Yealink usb-p1k usb phones. The audio part is enabled by the generic
	216	usb sound driver, so you might want to enable that as well.
	217
	218	For information about how to use these additional functions, see
	219	<file:Documentation/input/yealink.txt>.
	220
	221	To compile this driver as a module, choose M here: the module will be
	222	called yealink.
01387959	223
c04148f9 AH	224	config INPUT_CM109
	225	tristate "C-Media CM109 USB I/O Controller"
	226	depends on EXPERIMENTAL
	227	depends on USB_ARCH_HAS_HCD
	228	select USB
	229	help
	230	Say Y here if you want to enable keyboard and buzzer functions of the
	231	C-Media CM109 usb phones. The audio part is enabled by the generic
	232	usb sound driver, so you might want to enable that as well.
	233
	234	To compile this driver as a module, choose M here: the module will be
	235	called cm109.
	236
68d8bf04 FB	237	config INPUT_TWL4030_PWRBUTTON
	238	tristate "TWL4030 Power button Driver"
	239	depends on TWL4030_CORE
	240	help
	241	Say Y here if you want to enable power key reporting via the
	242	TWL4030 family of chips.
	243
	244	To compile this driver as a module, choose M here. The module will
	245	be called twl4030_pwrbutton.
	246
3dd1b394 JV	247	config INPUT_TWL4030_VIBRA
	248	tristate "Support for TWL4030 Vibrator"
	249	depends on TWL4030_CORE
	250	select TWL4030_CODEC
	251	select INPUT_FF_MEMLESS
	252	help
	253	This option enables support for TWL4030 Vibrator Driver.
	254
	255	To compile this driver as a module, choose M here. The module will
	256	be called twl4030_vibra.
	257
1da177e4 LT	258	config INPUT_UINPUT
	259	tristate "User level driver support"
	260	help
	261	Say Y here if you want to support user level drivers for input
	262	subsystem accessible under char device 10:223 - /dev/input/uinput.
	263
	264	To compile this driver as a module, choose M here: the
	265	module will be called uinput.
	266
48ad88b1 TB	267	config INPUT_SGI_BTNS
	268	tristate "SGI Indy/O2 volume button interface"
	269	depends on SGI_IP22 \|\| SGI_IP32
3bee2a04 TB	270	select INPUT_POLLDEV
3bee2a04 TB	271	help
48ad88b1	272	Say Y here if you want to support SGI Indy/O2 volume button interface.
3bee2a04 TB	273
3bee2a04 TB	274	To compile this driver as a module, choose M here: the
48ad88b1	275	module will be called sgi_btns.
3bee2a04	276
e258b80e DH	277	config INPUT_WINBOND_CIR
	278	tristate "Winbond IR remote control"
	279	depends on X86 && PNP
d2b5ec3a	280	select NEW_LEDS
e258b80e	281	select LEDS_CLASS
0baa3de6	282	select LEDS_TRIGGERS
e258b80e DH	283	select BITREVERSE
	284	help
	285	Say Y here if you want to use the IR remote functionality found
	286	in some Winbond SuperI/O chips. Currently only the WPCD376I
	287	chip is supported (included in some Intel Media series motherboards).
	288
	289	IR Receive and wake-on-IR from suspend and power-off is currently
	290	supported.
	291
	292	To compile this driver as a module, choose M here: the module will be
	293	called winbond_cir.
	294
1da177e4	295	config HP_SDC_RTC
bebb8a2b	296	tristate "HP SDC Real Time Clock"
d061ebd5	297	depends on (GSC \|\| HP300) && SERIO
1da177e4 LT	298	select HP_SDC
	299	help
	300	Say Y here if you want to support the built-in real time clock
	301	of the HP SDC controller.
	302
1851b06a BR	303	config INPUT_PCF50633_PMU
	304	tristate "PCF50633 PMU events"
	305	depends on MFD_PCF50633
	306	help
	307	Say Y to include support for delivering PMU events via input
	308	layer on NXP PCF50633.
	309
b91c4be7 BW	310	config INPUT_PCF8574
	311	tristate "PCF8574 Keypad input device"
	312	depends on I2C && EXPERIMENTAL
	313	help
	314	Say Y here if you want to support a keypad connetced via I2C
	315	with a PCF8574.
	316
	317	To compile this driver as a module, choose M here: the
	318	module will be called pcf8574_keypad.
	319
73969ff0 DM	320	config INPUT_GPIO_ROTARY_ENCODER
	321	tristate "Rotary encoders connected to GPIO pins"
	322	depends on GPIOLIB && GENERIC_GPIO
	323	help
	324	Say Y here to add support for rotary encoders connected to GPIO lines.
492d0f95	325	Check file:Documentation/input/rotary-encoder.txt for more
73969ff0 DM	326	information.
	327
	328	To compile this driver as a module, choose M here: the
	329	module will be called rotary_encoder.
	330
d9bdffd2 PS	331	config INPUT_RB532_BUTTON
	332	tristate "Mikrotik Routerboard 532 button interface"
	333	depends on MIKROTIK_RB532
	334	depends on GPIOLIB && GENERIC_GPIO
	335	select INPUT_POLLDEV
	336	help
	337	Say Y here if you want support for the S1 button built into
	338	Mikrotik's Routerboard 532.
	339
	340	To compile this driver as a module, choose M here: the
	341	module will be called rb532_button.
	342
eb990b55 DB	343	config INPUT_DM355EVM
	344	tristate "TI DaVinci DM355 EVM Keypad and IR Remote"
	345	depends on MFD_DM355EVM_MSP
66040727	346	select INPUT_SPARSEKMAP
eb990b55 DB	347	help
	348	Supports the pushbuttons and IR remote used with
	349	the DM355 EVM board.
	350
	351	To compile this driver as a module, choose M here: the
	352	module will be called dm355evm_keys.
48329582 MH	353
	354	config INPUT_BFIN_ROTARY
	355	tristate "Blackfin Rotary support"
	356	depends on BF54x \|\| BF52x
	357	help
	358	Say Y here if you want to use the Blackfin Rotary.
	359
	360	To compile this driver as a module, choose M here: the
	361	module will be called bfin-rotary.
	362
0c73b992 MB	363	config INPUT_WM831X_ON
	364	tristate "WM831X ON pin"
	365	depends on MFD_WM831X
	366	help
	367	Support the ON pin of WM831X PMICs as an input device
	368	reporting power button status.
	369
	370	To compile this driver as a module, choose M here: the module
	371	will be called wm831x_on.
	372
d0a82132 DR	373	config INPUT_PCAP
	374	tristate "Motorola EZX PCAP misc input events"
	375	depends on EZX_PCAP
	376	help
	377	Say Y here if you want to use Power key and Headphone button
	378	on Motorola EZX phones.
	379
	380	To compile this driver as a module, choose M here: the
	381	module will be called pcap_keys.
	382
1da177e4	383	endif