From: djkurtz@chromium.org
To: dmitry.torokhov@gmail.com, rydberg@euromail.se,
chase.douglas@canonical.com, rubini@cvml.unipv.it
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
derek.foreman@collabora.co.uk, daniel.stone@collabora.co.uk,
olofj@chromium.org, Daniel Kurtz <djkurtz@chromium.org>
Subject: [PATCH 7/9 v2] Input: synaptics - improved 2->3 finger transition handling
Date: Wed, 20 Jul 2011 21:39:04 +0800 [thread overview]
Message-ID: <1311169146-20066-8-git-send-email-djkurtz@chromium.org> (raw)
In-Reply-To: <1311169146-20066-1-git-send-email-djkurtz@chromium.org>
From: Daniel Kurtz <djkurtz@chromium.org>
As long as we know which slots are currently contained in SGM and AGM
packets, it is possible to track the slot 0 finger when transitioning from
2->3 fingers. This is the case when fingers are being added one at a
time, 1->2->3.
However, when fingers are removed, we sometimes lose track of which slots
are contained in SGM and AGM. In particular, when transitioning from 3->2
and sometimes 3->1. In both of these cases, we can no longer track slot 0
during 2->3 transitions.
Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
---
drivers/input/mouse/synaptics.c | 33 +++++++++++++++++++++++++++------
drivers/input/mouse/synaptics.h | 1 +
2 files changed, 28 insertions(+), 6 deletions(-)
diff --git a/drivers/input/mouse/synaptics.c b/drivers/input/mouse/synaptics.c
index b626b98..893e567 100644
--- a/drivers/input/mouse/synaptics.c
+++ b/drivers/input/mouse/synaptics.c
@@ -659,6 +659,7 @@ static void synaptics_image_sensor_0f(struct synaptics_data *priv,
struct synaptics_mt_state *mt_state)
{
synaptics_mt_state_set(mt_state, 0, -1, -1);
+ priv->mt_state_lost = false;
}
/* Handle case where mt_state->count = 1 */
@@ -726,6 +727,7 @@ static void synaptics_image_sensor_1f(struct synaptics_data *priv,
* So, empty all slots. We will guess slot 0 on subsequent 1->1
*/
synaptics_mt_state_set(mt_state, 0, -1, -1);
+ priv->mt_state_lost = true;
break;
}
}
@@ -771,6 +773,7 @@ static void synaptics_image_sensor_2f(struct synaptics_data *priv,
* subsequent 2->2
*/
synaptics_mt_state_set(mt_state, 0, -1, -1);
+ priv->mt_state_lost = true;
break;
}
}
@@ -800,14 +803,32 @@ static void synaptics_image_sensor_3f(struct synaptics_data *priv,
break;
case 2:
/*
- * On 2->3 transitions, we are given no indication which finger
- * was added.
- * We don't even know what finger the current AGM packet
- * contained.
+ * After some 3->1 and all 3->2 transitions, we lose track
+ * of which slot is reported by sgm and agm.
*
- * So, empty all slots. They get filled on a subsequent 3->3
+ * For 2->3 in this state, empty all slots, and we will guess
+ * (0,1) on a subsequent 0->3.
+ *
+ * To userspace, the resulting transition will look like:
+ * 2:[0,1] -> 0:[-1,-1] -> 3:[0,2]
*/
- synaptics_mt_state_set(mt_state, 0, -1, -1);
+ if (priv->mt_state_lost) {
+ synaptics_mt_state_set(mt_state, 0, -1, -1);
+ break;
+ }
+
+ /*
+ * If the (SGM,AGM) really previously contained slots (0, 1),
+ * then we cannot know what slot was just reported by the AGM,
+ * because the 2->3 transition can occur either before or after
+ * the AGM packet. Thus, this most recent AGM could contain
+ * either the same old slot 1 or the new slot 2.
+ * Subsequent AGMs will be reporting slot 2.
+ *
+ * To userspace, the resulting transition will look like:
+ * 2:[0,1] -> 1:[0,-1] -> 3:[0,2]
+ */
+ synaptics_mt_state_set(mt_state, 1, 0, -1);
break;
case 3:
/*
diff --git a/drivers/input/mouse/synaptics.h b/drivers/input/mouse/synaptics.h
index 87be1fe..e3edfea 100644
--- a/drivers/input/mouse/synaptics.h
+++ b/drivers/input/mouse/synaptics.h
@@ -162,6 +162,7 @@ struct synaptics_data {
struct serio *pt_port; /* Pass-through serio port */
struct synaptics_mt_state mt_state; /* Current mt finger state */
+ bool mt_state_lost; /* mt_state may be incorrect */
/*
* Last received Advanced Gesture Mode (AGM) packet. An AGM packet
--
1.7.3.1
next prev parent reply other threads:[~2011-07-20 13:39 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 13:38 [PATCH 0/9 v2] Synaptics image sensor support djkurtz
2011-07-20 13:38 ` [PATCH 1/9 v2] Input: synaptics - refactor y inversion djkurtz
2011-07-23 0:30 ` Chase Douglas
2011-07-25 8:27 ` Dmitry Torokhov
2011-07-26 2:19 ` Daniel Kurtz
2011-07-26 22:59 ` Chase Douglas
2011-07-20 13:38 ` [PATCH 2/9 v2] Input: synaptics - refactor agm packet parsing djkurtz
2011-07-23 0:32 ` Chase Douglas
2011-07-20 13:39 ` [PATCH 3/9 v2] Input: synaptics - refactor initialization of abs position axes djkurtz
2011-07-23 0:36 ` Chase Douglas
2011-07-20 13:39 ` [PATCH 4/9 v2] Input: synaptics - add image sensor support djkurtz
2011-07-20 13:39 ` [PATCH 5/9 v2] Input: synaptics - decode AGM packet types djkurtz
2011-07-20 13:39 ` [PATCH 6/9 v2] Input: synaptics - process finger (<=3) transitions djkurtz
2011-07-23 1:11 ` Chase Douglas
2011-07-20 13:39 ` djkurtz [this message]
2011-07-23 1:07 ` [PATCH 7/9 v2] Input: synaptics - improved 2->3 finger transition handling Chase Douglas
2011-07-23 4:36 ` Daniel Kurtz
2011-07-26 23:14 ` Chase Douglas
2011-07-27 4:48 ` Daniel Kurtz
2011-07-27 21:13 ` Chase Douglas
2011-07-28 1:00 ` Daniel Kurtz
2011-07-28 2:07 ` Chase Douglas
2011-07-28 13:56 ` Daniel Kurtz
2011-07-28 17:31 ` Chase Douglas
2011-07-20 13:39 ` [PATCH 8/9 v2] Input: add BTN_TOOL_QUINTTAP for reporting 5 fingers on touchpad djkurtz
2011-07-23 0:59 ` Chase Douglas
2011-07-25 8:29 ` Dmitry Torokhov
2011-07-25 9:14 ` Daniel Kurtz
2011-07-25 18:16 ` Dmitry Torokhov
2011-07-26 2:18 ` Daniel Kurtz
2011-08-11 20:07 ` Henrik Rydberg
2011-07-26 23:03 ` Chase Douglas
2011-07-20 13:39 ` [PATCH 9/9 v2] Input: synaptics - process finger (<=5) transitions djkurtz
2011-07-23 1:02 ` Chase Douglas
2011-07-23 4:11 ` Daniel Kurtz
2011-07-26 23:17 ` Chase Douglas
2011-07-23 1:13 ` [PATCH 0/9 v2] Synaptics image sensor support Chase Douglas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1311169146-20066-8-git-send-email-djkurtz@chromium.org \
--to=djkurtz@chromium.org \
--cc=chase.douglas@canonical.com \
--cc=daniel.stone@collabora.co.uk \
--cc=derek.foreman@collabora.co.uk \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olofj@chromium.org \
--cc=rubini@cvml.unipv.it \
--cc=rydberg@euromail.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).