Thread (2 messages) 2 messages, 2 authors, 2012-01-11

Re: [PATCH v2] Documented input device properties.

From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Date: 2012-01-11 17:43:19

On Wed, Jan 11, 2012 at 01:56:31PM +0200, Jussi Pakkanen wrote:
quoted hunk ↗ jump to hunk
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.
What exactly do you mean by "touch-based input"? Is a touchpad
touch-based or not? Going by this paragraph it should not have
INPUT_PROP_POINTER property, but in fact we do set it at least on
Synaptics touchpads.

Thanks.

-- 
Dmitry
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help