Kconfig 6.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218
  1. #
  2. # Input device configuration
  3. #
  4. menu "Input device support"
  5. depends on !UML
  6. config INPUT
  7. tristate "Generic input layer (needed for keyboard, mouse, ...)" if EXPERT
  8. default y
  9. help
  10. Say Y here if you have any input device (mouse, keyboard, tablet,
  11. joystick, steering wheel ...) connected to your system and want
  12. it to be available to applications. This includes standard PS/2
  13. keyboard and mouse.
  14. Say N here if you have a headless (no monitor, no keyboard) system.
  15. More information is available: <file:Documentation/input/input.txt>
  16. If unsure, say Y.
  17. To compile this driver as a module, choose M here: the
  18. module will be called input.
  19. if INPUT
  20. config INPUT_LEDS
  21. tristate "Export input device LEDs in sysfs"
  22. depends on LEDS_CLASS
  23. default INPUT
  24. help
  25. Say Y here if you would like to export LEDs on input devices
  26. as standard LED class devices in sysfs.
  27. If unsure, say Y.
  28. To compile this driver as a module, choose M here: the
  29. module will be called input-leds.
  30. config INPUT_FF_MEMLESS
  31. tristate "Support for memoryless force-feedback devices"
  32. help
  33. Say Y here if you have memoryless force-feedback input device
  34. such as Logitech WingMan Force 3D, ThrustMaster FireStorm Dual
  35. Power 2, or similar. You will also need to enable hardware-specific
  36. driver.
  37. If unsure, say N.
  38. To compile this driver as a module, choose M here: the
  39. module will be called ff-memless.
  40. config INPUT_POLLDEV
  41. tristate "Polled input device skeleton"
  42. help
  43. Say Y here if you are using a driver for an input
  44. device that periodically polls hardware state. This
  45. option is only useful for out-of-tree drivers since
  46. in-tree drivers select it automatically.
  47. If unsure, say N.
  48. To compile this driver as a module, choose M here: the
  49. module will be called input-polldev.
  50. config INPUT_SPARSEKMAP
  51. tristate "Sparse keymap support library"
  52. help
  53. Say Y here if you are using a driver for an input
  54. device that uses sparse keymap. This option is only
  55. useful for out-of-tree drivers since in-tree drivers
  56. select it automatically.
  57. If unsure, say N.
  58. To compile this driver as a module, choose M here: the
  59. module will be called sparse-keymap.
  60. config INPUT_MATRIXKMAP
  61. tristate "Matrix keymap support library"
  62. help
  63. Say Y here if you are using a driver for an input
  64. device that uses matrix keymap. This option is only
  65. useful for out-of-tree drivers since in-tree drivers
  66. select it automatically.
  67. If unsure, say N.
  68. To compile this driver as a module, choose M here: the
  69. module will be called matrix-keymap.
  70. comment "Userland interfaces"
  71. config INPUT_MOUSEDEV
  72. tristate "Mouse interface"
  73. default y
  74. help
  75. Say Y here if you want your mouse to be accessible as char devices
  76. 13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice as an
  77. emulated IntelliMouse Explorer PS/2 mouse. That way, all user space
  78. programs (including SVGAlib, GPM and X) will be able to use your
  79. mouse.
  80. If unsure, say Y.
  81. To compile this driver as a module, choose M here: the
  82. module will be called mousedev.
  83. config INPUT_MOUSEDEV_PSAUX
  84. bool "Provide legacy /dev/psaux device"
  85. default y
  86. depends on INPUT_MOUSEDEV
  87. help
  88. Say Y here if you want your mouse also be accessible as char device
  89. 10:1 - /dev/psaux. The data available through /dev/psaux is exactly
  90. the same as the data from /dev/input/mice.
  91. If unsure, say Y.
  92. config INPUT_MOUSEDEV_SCREEN_X
  93. int "Horizontal screen resolution"
  94. depends on INPUT_MOUSEDEV
  95. default "1024"
  96. help
  97. If you're using a digitizer, or a graphic tablet, and want to use
  98. it as a mouse then the mousedev driver needs to know the X window
  99. screen resolution you are using to correctly scale the data. If
  100. you're not using a digitizer, this value is ignored.
  101. config INPUT_MOUSEDEV_SCREEN_Y
  102. int "Vertical screen resolution"
  103. depends on INPUT_MOUSEDEV
  104. default "768"
  105. help
  106. If you're using a digitizer, or a graphic tablet, and want to use
  107. it as a mouse then the mousedev driver needs to know the X window
  108. screen resolution you are using to correctly scale the data. If
  109. you're not using a digitizer, this value is ignored.
  110. config INPUT_JOYDEV
  111. tristate "Joystick interface"
  112. help
  113. Say Y here if you want your joystick or gamepad to be
  114. accessible as char device 13:0+ - /dev/input/jsX device.
  115. If unsure, say Y.
  116. More information is available: <file:Documentation/input/joystick.txt>
  117. To compile this driver as a module, choose M here: the
  118. module will be called joydev.
  119. config INPUT_EVDEV
  120. tristate "Event interface"
  121. help
  122. Say Y here if you want your input device events be accessible
  123. under char device 13:64+ - /dev/input/eventX in a generic way.
  124. To compile this driver as a module, choose M here: the
  125. module will be called evdev.
  126. config INPUT_EVBUG
  127. tristate "Event debugging"
  128. help
  129. Say Y here if you have a problem with the input subsystem and
  130. want all events (keypresses, mouse movements), to be output to
  131. the system log. While this is useful for debugging, it's also
  132. a security threat - your keypresses include your passwords, of
  133. course.
  134. If unsure, say N.
  135. To compile this driver as a module, choose M here: the
  136. module will be called evbug.
  137. config INPUT_APMPOWER
  138. tristate "Input Power Event -> APM Bridge" if EXPERT
  139. depends on INPUT && APM_EMULATION
  140. help
  141. Say Y here if you want suspend key events to trigger a user
  142. requested suspend through APM. This is useful on embedded
  143. systems where such behaviour is desired without userspace
  144. interaction. If unsure, say N.
  145. To compile this driver as a module, choose M here: the
  146. module will be called apm-power.
  147. comment "Input Device Drivers"
  148. source "drivers/input/keyboard/Kconfig"
  149. source "drivers/input/mouse/Kconfig"
  150. source "drivers/input/joystick/Kconfig"
  151. source "drivers/input/tablet/Kconfig"
  152. source "drivers/input/touchscreen/Kconfig"
  153. source "drivers/input/misc/Kconfig"
  154. source "drivers/input/rmi4/Kconfig"
  155. endif
  156. menu "Hardware I/O ports"
  157. source "drivers/input/serio/Kconfig"
  158. source "drivers/input/gameport/Kconfig"
  159. endmenu
  160. endmenu