drivers/input/Kconfig

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