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