From: Daniel Kurtz <djkurtz@chromium.org>
To: Chase Douglas <chase.douglas@canonical.com>
Cc: dmitry.torokhov@gmail.com, rydberg@euromail.se,
rubini@cvml.unipv.it, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, derek.foreman@collabora.co.uk,
daniel.stone@collabora.co.uk, olofj@chromium.org
Subject: Re: [PATCH 9/9 v2] Input: synaptics - process finger (<=5) transitions
Date: Sat, 23 Jul 2011 12:11:18 +0800 [thread overview]
Message-ID: <CAGS+omABdrRjZ0nsajAB3WRj2WASUYKMfAaPeaOWuhUfLUFMeQ@mail.gmail.com> (raw)
In-Reply-To: <4E2A1D9A.2090704@canonical.com>
Hi Chase,
Thanks for all of your reviews!
On Sat, Jul 23, 2011 at 9:02 AM, Chase Douglas
<chase.douglas@canonical.com> wrote:
>
> On 07/20/2011 06:39 AM, djkurtz@chromium.org wrote:
> > From: Daniel Kurtz <djkurtz@chromium.org>
> >
> > Synaptics image sensor touchpads track up to 5 fingers, but only report 2.
> > They use a special "TYPE=2" (AGM-CONTACT) packet type that reports
> > the number of tracked fingers and which finger is reported in the SGM
> > and AGM packets.
> >
> > With this new packet type, it is possible to tell userspace when 4 or 5
> > fingers are touching.
>
> Maybe I'm blind, but I don't see where the QUADTAP and QUINTAP values
> are set in the events. I see where the bits are set during
> initialization, but not during use.
It's subtle.
The firmware actually report 4/5 in the AGM-CONTACT packet, which the
agm packet parser sets directly in mt_state->count.
This is then reported to userspace when synaptics_report_mt() calls
input_mt_report_finger_count(dev, mt_state->count), which now supports
QUINTTAP (see patch #8).
-Daniel
>
> > Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
> > ---
> > drivers/input/mouse/synaptics.c | 44 ++++++++++++++++++++++++++++++++++++++-
> > 1 files changed, 43 insertions(+), 1 deletions(-)
> >
> > diff --git a/drivers/input/mouse/synaptics.c b/drivers/input/mouse/synaptics.c
> > index 893e567..2a1e05f 100644
> > --- a/drivers/input/mouse/synaptics.c
> > +++ b/drivers/input/mouse/synaptics.c
> > @@ -729,6 +729,10 @@ static void synaptics_image_sensor_1f(struct synaptics_data *priv,
> > synaptics_mt_state_set(mt_state, 0, -1, -1);
> > priv->mt_state_lost = true;
> > break;
> > + case 4:
> > + case 5:
> > + /* mt_state was updated by AGM-CONTACT packet */
> > + break;
> > }
> > }
> >
> > @@ -775,6 +779,10 @@ static void synaptics_image_sensor_2f(struct synaptics_data *priv,
> > synaptics_mt_state_set(mt_state, 0, -1, -1);
> > priv->mt_state_lost = true;
> > break;
> > + case 4:
> > + case 5:
> > + /* mt_state was updated by AGM-CONTACT packet */
> > + break;
> > }
> > }
> >
> > @@ -803,6 +811,22 @@ static void synaptics_image_sensor_3f(struct synaptics_data *priv,
> > break;
> > case 2:
> > /*
> > + * If the AGM previously contained slot 3 or higher, then the
> > + * newly touching finger is in the lowest available slot.
> > + *
> > + * If SGM was previously 1 or higher, then the new SGM is
> > + * now slot 0 (with a new finger), otherwise, the new finger
> > + * is now in a hidden slot between 0 and AGM's slot.
> > + *
> > + * In all such cases, the SGM now contains slot 0, and the AGM
> > + * continues to contain the same slot as before.
> > + */
> > + if (old->agm >= 3) {
> > + synaptics_mt_state_set(mt_state, 3, 0, old->agm);
> > + break;
> > + }
> > +
> > + /*
> > * After some 3->1 and all 3->2 transitions, we lose track
> > * of which slot is reported by sgm and agm.
> > *
> > @@ -836,9 +860,22 @@ static void synaptics_image_sensor_3f(struct synaptics_data *priv,
> > * received AGM-CONTACT packet.
> > */
> > break;
> > +
> > + case 4:
> > + case 5:
> > + /* mt_state was updated by AGM-CONTACT packet */
> > + break;
> > }
> > }
> >
> > +/* Handle case where mt_state->count = 4, or = 5 */
> > +static void synaptics_image_sensor_45f(struct synaptics_data *priv,
> > + struct synaptics_mt_state *mt_state)
> > +{
> > + /* mt_state was updated correctly by AGM-CONTACT packet */
> > + priv->mt_state_lost = false;
> > +}
> > +
> > static void synaptics_image_sensor_process(struct psmouse *psmouse,
> > struct synaptics_hw_state *sgm)
> > {
> > @@ -858,8 +895,10 @@ static void synaptics_image_sensor_process(struct psmouse *psmouse,
> > synaptics_image_sensor_1f(priv, &mt_state);
> > else if (sgm->w == 0)
> > synaptics_image_sensor_2f(priv, &mt_state);
> > - else if (sgm->w == 1)
> > + else if (sgm->w == 1 && mt_state.count <= 3)
> > synaptics_image_sensor_3f(priv, &mt_state);
> > + else
> > + synaptics_image_sensor_45f(priv, &mt_state);
> >
> > /* Send resulting input events to user space */
> > synaptics_report_mt(psmouse, &mt_state, sgm);
> > @@ -1078,6 +1117,9 @@ static void set_input_params(struct input_dev *dev, struct synaptics_data *priv)
> > input_set_abs_params(dev, ABS_MT_PRESSURE, 0, 255, 0, 0);
> > /* Image sensors can sometimes report per-contact width */
> > input_set_abs_params(dev, ABS_MT_TOUCH_MAJOR, 4, 15, 0, 0);
> > + /* Image sensors can signal 4 and 5 finger clicks */
> > + __set_bit(BTN_TOOL_QUADTAP, dev->keybit);
> > + __set_bit(BTN_TOOL_QUINTTAP, dev->keybit);
> > } else if (SYN_CAP_ADV_GESTURE(priv->ext_cap_0c)) {
> > /* Non-image sensors with AGM use semi-mt */
> > __set_bit(INPUT_PROP_SEMI_MT, dev->propbit);
>
next prev parent reply other threads:[~2011-07-23 4:11 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 ` [PATCH 7/9 v2] Input: synaptics - improved 2->3 finger transition handling djkurtz
2011-07-23 1:07 ` 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 [this message]
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=CAGS+omABdrRjZ0nsajAB3WRj2WASUYKMfAaPeaOWuhUfLUFMeQ@mail.gmail.com \
--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).