drivers/input/Kconfig

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