[PATCH v2] Documented input device properties.
From: Jussi Pakkanen <hidden>
Date: 2012-01-11 11:56:32
Subsystem:
documentation, input (keyboard, mouse, joystick, touchscreen) drivers, the rest · Maintainers:
Jonathan Corbet, Dmitry Torokhov, Linus Torvalds
Signed-off-by: Jussi Pakkanen <redacted> --- Documentation/input/event-codes.txt | 34 ++++++++++++++++++++++++++++++++++ 1 files changed, 34 insertions(+), 0 deletions(-)
diff --git a/Documentation/input/event-codes.txt b/Documentation/input/event-codes.txt
index 23fcb05..2c4add3 100644
--- a/Documentation/input/event-codes.txt
+++ b/Documentation/input/event-codes.txt@@ -220,6 +220,40 @@ EV_PWR: EV_PWR events are a special type of event used specifically for power mangement. Its usage is not well defined. To be addressed later. +Device properties: +================= + +INPUT_PROP_POINTER: +------------------ + +There does not exist a one to one mapping between the device +coordinates and screen coordinates. This property only has meaning for +non-touch based input such as a pen or an eraser. + +INPUT_PROP_DIRECT: +------------------ + +The device coordinates can be directly mapped to screen coordinates +(i.e. the opposite of INPUT_PROP_POINTER) This property only has +meaning for touch-based input. An example would be a touchscreen. + +INPUT_PROP_BUTTONPAD: +-------------------- + +The device has one or more physical buttons beneath the active surface +area. This means that you can generate button clicks by pressing down +on the trackpad area. Examples include aluminium body MacBook +trackpads and Synaptics clickpads. + +INPUT_PROP_SEMI_MT: +------------------ + +The device is a semi multitouch device. This means that it does not +provide proper touch locations; it only reports the total number of +touches and a bounding box that is defined by two of the +touches. There is no way to know which two touches the device chooses +to report. + Guidelines: ========== The guidelines below ensure proper single-touch and multi-finger functionality.
--
1.7.5.4