drivers/input/misc/Kconfig

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