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