Kconfig 4.2 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157
  1. #
  2. # Input device configuration
  3. #
  4. menu "Input device support"
  5. config INPUT
  6. tristate "Generic input layer (needed for keyboard, mouse, ...)" if EMBEDDED
  7. default y
  8. ---help---
  9. Say Y here if you have any input device (mouse, keyboard, tablet,
  10. joystick, steering wheel ...) connected to your system and want
  11. it to be available to applications. This includes standard PS/2
  12. keyboard and mouse.
  13. Say N here if you have a headless (no monitor, no keyboard) system.
  14. More information is available: <file:Documentation/input/input.txt>
  15. If unsure, say Y.
  16. To compile this driver as a module, choose M here: the
  17. module will be called input.
  18. if INPUT
  19. comment "Userland interfaces"
  20. config INPUT_MOUSEDEV
  21. tristate "Mouse interface" if EMBEDDED
  22. default y
  23. ---help---
  24. Say Y here if you want your mouse to be accessible as char devices
  25. 13:32+ - /dev/input/mouseX and 13:63 - /dev/input/mice as an
  26. emulated IntelliMouse Explorer PS/2 mouse. That way, all user space
  27. programs (including SVGAlib, GPM and X) will be able to use your
  28. mouse.
  29. If unsure, say Y.
  30. To compile this driver as a module, choose M here: the
  31. module will be called mousedev.
  32. config INPUT_MOUSEDEV_PSAUX
  33. bool "Provide legacy /dev/psaux device"
  34. default y
  35. depends on INPUT_MOUSEDEV
  36. ---help---
  37. Say Y here if you want your mouse also be accessible as char device
  38. 10:1 - /dev/psaux. The data available through /dev/psaux is exactly
  39. the same as the data from /dev/input/mice.
  40. If unsure, say Y.
  41. config INPUT_MOUSEDEV_SCREEN_X
  42. int "Horizontal screen resolution"
  43. depends on INPUT_MOUSEDEV
  44. default "1024"
  45. help
  46. If you're using a digitizer, or a graphic tablet, and want to use
  47. it as a mouse then the mousedev driver needs to know the X window
  48. screen resolution you are using to correctly scale the data. If
  49. you're not using a digitizer, this value is ignored.
  50. config INPUT_MOUSEDEV_SCREEN_Y
  51. int "Vertical screen resolution"
  52. depends on INPUT_MOUSEDEV
  53. default "768"
  54. help
  55. If you're using a digitizer, or a graphic tablet, and want to use
  56. it as a mouse then the mousedev driver needs to know the X window
  57. screen resolution you are using to correctly scale the data. If
  58. you're not using a digitizer, this value is ignored.
  59. config INPUT_JOYDEV
  60. tristate "Joystick interface"
  61. ---help---
  62. Say Y here if you want your joystick or gamepad to be
  63. accessible as char device 13:0+ - /dev/input/jsX device.
  64. If unsure, say Y.
  65. More information is available: <file:Documentation/input/joystick.txt>
  66. To compile this driver as a module, choose M here: the
  67. module will be called joydev.
  68. config INPUT_TSDEV
  69. tristate "Touchscreen interface"
  70. ---help---
  71. Say Y here if you have an application that only can understand the
  72. Compaq touchscreen protocol for absolute pointer data. This is
  73. useful namely for embedded configurations.
  74. If unsure, say N.
  75. To compile this driver as a module, choose M here: the
  76. module will be called tsdev.
  77. config INPUT_TSDEV_SCREEN_X
  78. int "Horizontal screen resolution"
  79. depends on INPUT_TSDEV
  80. default "240"
  81. config INPUT_TSDEV_SCREEN_Y
  82. int "Vertical screen resolution"
  83. depends on INPUT_TSDEV
  84. default "320"
  85. config INPUT_EVDEV
  86. tristate "Event interface"
  87. help
  88. Say Y here if you want your input device events be accessible
  89. under char device 13:64+ - /dev/input/eventX in a generic way.
  90. To compile this driver as a module, choose M here: the
  91. module will be called evdev.
  92. config INPUT_EVBUG
  93. tristate "Event debugging"
  94. ---help---
  95. Say Y here if you have a problem with the input subsystem and
  96. want all events (keypresses, mouse movements), to be output to
  97. the system log. While this is useful for debugging, it's also
  98. a security threat - your keypresses include your passwords, of
  99. course.
  100. If unsure, say N.
  101. To compile this driver as a module, choose M here: the
  102. module will be called evbug.
  103. comment "Input Device Drivers"
  104. source "drivers/input/keyboard/Kconfig"
  105. source "drivers/input/mouse/Kconfig"
  106. source "drivers/input/joystick/Kconfig"
  107. source "drivers/input/touchscreen/Kconfig"
  108. source "drivers/input/misc/Kconfig"
  109. endif
  110. menu "Hardware I/O ports"
  111. source "drivers/input/serio/Kconfig"
  112. source "drivers/input/gameport/Kconfig"
  113. endmenu
  114. endmenu