Kconfig 6.0 KB

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