Kconfig 5.7 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184
  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. If unsure, say Y.
  11. if INPUT_MISC
  12. config INPUT_PCSPKR
  13. tristate "PC Speaker support"
  14. depends on ALPHA || X86 || MIPS || PPC_PREP || PPC_CHRP || PPC_PSERIES
  15. help
  16. Say Y here if you want the standard PC Speaker to be used for
  17. bells and whistles.
  18. If unsure, say Y.
  19. To compile this driver as a module, choose M here: the
  20. module will be called pcspkr.
  21. config INPUT_SPARCSPKR
  22. tristate "SPARC Speaker support"
  23. depends on PCI && SPARC64
  24. help
  25. Say Y here if you want the standard Speaker on Sparc PCI systems
  26. to be used for bells and whistles.
  27. If unsure, say Y.
  28. To compile this driver as a module, choose M here: the
  29. module will be called sparcspkr.
  30. config INPUT_M68K_BEEP
  31. tristate "M68k Beeper support"
  32. depends on M68K
  33. config INPUT_IXP4XX_BEEPER
  34. tristate "IXP4XX Beeper support"
  35. depends on ARCH_IXP4XX
  36. help
  37. If you say yes here, you can connect a beeper to the
  38. ixp4xx gpio pins. This is used by the LinkSys NSLU2.
  39. If unsure, say Y.
  40. To compile this driver as a module, choose M here: the
  41. module will be called ixp4xx-beeper.
  42. config INPUT_COBALT_BTNS
  43. tristate "Cobalt button interface"
  44. depends on MIPS_COBALT
  45. select INPUT_POLLDEV
  46. help
  47. Say Y here if you want to support MIPS Cobalt button interface.
  48. To compile this driver as a module, choose M here: the
  49. module will be called cobalt_btns.
  50. config INPUT_WISTRON_BTNS
  51. tristate "x86 Wistron laptop button interface"
  52. depends on X86 && !X86_64
  53. select NEW_LEDS
  54. select LEDS_CLASS
  55. help
  56. Say Y here for support of Winstron laptop button interface, used on
  57. laptops of various brands, including Acer and Fujitsu-Siemens. If
  58. available, mail and wifi leds will be controlable via /sys/class/leds.
  59. To compile this driver as a module, choose M here: the module will
  60. be called wistron_btns.
  61. config INPUT_ATLAS_BTNS
  62. tristate "x86 Atlas button interface"
  63. depends on X86 && ACPI
  64. help
  65. Say Y here for support of Atlas wallmount touchscreen buttons.
  66. The events will show up as scancodes F1 through F9 via evdev.
  67. To compile this driver as a module, choose M here: the module will
  68. be called atlas_btns.
  69. config INPUT_ATI_REMOTE
  70. tristate "ATI / X10 USB RF remote control"
  71. depends on USB_ARCH_HAS_HCD
  72. select USB
  73. help
  74. Say Y here if you want to use an ATI or X10 "Lola" USB remote control.
  75. These are RF remotes with USB receivers.
  76. The ATI remote comes with many of ATI's All-In-Wonder video cards.
  77. The X10 "Lola" remote is available at:
  78. <http://www.x10.com/products/lola_sg1.htm>
  79. This driver provides mouse pointer, left and right mouse buttons,
  80. and maps all the other remote buttons to keypress events.
  81. To compile this driver as a module, choose M here: the module will be
  82. called ati_remote.
  83. config INPUT_ATI_REMOTE2
  84. tristate "ATI / Philips USB RF remote control"
  85. depends on USB_ARCH_HAS_HCD
  86. select USB
  87. help
  88. Say Y here if you want to use an ATI or Philips USB RF remote control.
  89. These are RF remotes with USB receivers.
  90. ATI Remote Wonder II comes with some ATI's All-In-Wonder video cards
  91. and is also available as a separate product.
  92. This driver provides mouse pointer, left and right mouse buttons,
  93. and maps all the other remote buttons to keypress events.
  94. To compile this driver as a module, choose M here: the module will be
  95. called ati_remote2.
  96. config INPUT_KEYSPAN_REMOTE
  97. tristate "Keyspan DMR USB remote control (EXPERIMENTAL)"
  98. depends on EXPERIMENTAL
  99. depends on USB_ARCH_HAS_HCD
  100. select USB
  101. help
  102. Say Y here if you want to use a Keyspan DMR USB remote control.
  103. Currently only the UIA-11 type of receiver has been tested. The tag
  104. on the receiver that connects to the USB port should have a P/N that
  105. will tell you what type of DMR you have. The UIA-10 type is not
  106. supported at this time. This driver maps all buttons to keypress
  107. events.
  108. To compile this driver as a module, choose M here: the module will
  109. be called keyspan_remote.
  110. config INPUT_POWERMATE
  111. tristate "Griffin PowerMate and Contour Jog support"
  112. depends on USB_ARCH_HAS_HCD
  113. select USB
  114. help
  115. Say Y here if you want to use Griffin PowerMate or Contour Jog devices.
  116. These are aluminum dials which can measure clockwise and anticlockwise
  117. rotation. The dial also acts as a pushbutton. The base contains an LED
  118. which can be instructed to pulse or to switch to a particular intensity.
  119. You can download userspace tools from
  120. <http://sowerbutts.com/powermate/>.
  121. To compile this driver as a module, choose M here: the
  122. module will be called powermate.
  123. config INPUT_YEALINK
  124. tristate "Yealink usb-p1k voip phone"
  125. depends EXPERIMENTAL
  126. depends on USB_ARCH_HAS_HCD
  127. select USB
  128. help
  129. Say Y here if you want to enable keyboard and LCD functions of the
  130. Yealink usb-p1k usb phones. The audio part is enabled by the generic
  131. usb sound driver, so you might want to enable that as well.
  132. For information about how to use these additional functions, see
  133. <file:Documentation/input/yealink.txt>.
  134. To compile this driver as a module, choose M here: the module will be
  135. called yealink.
  136. config INPUT_UINPUT
  137. tristate "User level driver support"
  138. help
  139. Say Y here if you want to support user level drivers for input
  140. subsystem accessible under char device 10:223 - /dev/input/uinput.
  141. To compile this driver as a module, choose M here: the
  142. module will be called uinput.
  143. config HP_SDC_RTC
  144. tristate "HP SDC Real Time Clock"
  145. depends on GSC || HP300
  146. select HP_SDC
  147. help
  148. Say Y here if you want to support the built-in real time clock
  149. of the HP SDC controller.
  150. endif