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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Say Y here if you want to support the built-in real time clock of the HP SDC controller.
Say Y to include support for delivering PMU events via input layer on NXP PCF50633.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.