Blame - drivers/input/Kconfig - android_kernel_htc_msm8960

blob: 58223b5d842a00059c9d6b0ee30a45417fd0961a [file] [log] [blame]

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