From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Peter Hutterer <peter.hutterer@who-t.net>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] Input - synaptics: fix middle button on Lenovo 2015 products
Date: Wed, 4 Feb 2015 11:53:59 -0800 [thread overview]
Message-ID: <20150204195359.GD15782@dtor-ws> (raw)
In-Reply-To: <20150204194332.GC16434@mail.corp.redhat.com>
On Wed, Feb 04, 2015 at 02:43:32PM -0500, Benjamin Tissoires wrote:
> On Feb 02 2015 or thereabouts, Dmitry Torokhov wrote:
> > On Wed, Jan 28, 2015 at 03:10:04PM -0500, Benjamin Tissoires wrote:
> > > On the X1 Carbon 3rd gen (with a 2015 broadwell cpu), the physical middle
> > > button of the trackstick (attached to the touchpad serio device, of course)
> > > seems to get lost.
> > >
> > > Actually, the touchpads reports 3 extra buttons, which falls in the switch
> > > below to the '2' case. Let's handle the case of odd numbers also, so that
> > > the middle button finds its way back.
> > >
> > > Cc: stable@vger.kernel.org
> > > Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
> > > ---
> > > drivers/input/mouse/synaptics.c | 6 +++++-
> > > 1 file changed, 5 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/input/mouse/synaptics.c b/drivers/input/mouse/synaptics.c
> > > index f89de89..0d12664 100644
> > > --- a/drivers/input/mouse/synaptics.c
> > > +++ b/drivers/input/mouse/synaptics.c
> > > @@ -689,7 +689,7 @@ static int synaptics_parse_hw_state(const unsigned char buf[],
> > >
> > > if (SYN_CAP_MULTI_BUTTON_NO(priv->ext_cap) &&
> > > ((buf[0] ^ buf[3]) & 0x02)) {
> > > - switch (SYN_CAP_MULTI_BUTTON_NO(priv->ext_cap) & ~0x01) {
> > > + switch (SYN_CAP_MULTI_BUTTON_NO(priv->ext_cap)) {
> > > default:
> > > /*
> > > * if nExtBtn is greater than 8 it should be
> > > @@ -698,15 +698,19 @@ static int synaptics_parse_hw_state(const unsigned char buf[],
> > > break;
> > > case 8:
> > > hw->ext_buttons |= ((buf[5] & 0x08)) ? 0x80 : 0;
> > > + case 7:
> > > hw->ext_buttons |= ((buf[4] & 0x08)) ? 0x40 : 0;
> > > case 6:
> > > hw->ext_buttons |= ((buf[5] & 0x04)) ? 0x20 : 0;
> > > + case 5:
> > > hw->ext_buttons |= ((buf[4] & 0x04)) ? 0x10 : 0;
> > > case 4:
> > > hw->ext_buttons |= ((buf[5] & 0x02)) ? 0x08 : 0;
> > > + case 3:
> > > hw->ext_buttons |= ((buf[4] & 0x02)) ? 0x04 : 0;
> > > case 2:
> > > hw->ext_buttons |= ((buf[5] & 0x01)) ? 0x02 : 0;
> > > + case 1:
> > > hw->ext_buttons |= ((buf[4] & 0x01)) ? 0x01 : 0;
> > > }
> > > }
> >
> > Hmm, that switch has gotten unwieldy. Maybe we can do someting like
> > this:
>
> Minus a typo, it works too.
>
> Though I must say even if the switch is ugly, it's a no brainer to
> understand what is this about. Here, it requires a little bit more
> skills :)
Yeah, it really wasn't about making code that much clearer but rather
about number of operations we need to make to figure button state.
Switch plus bazillion of ternary operations results in many many
branches, the new version does not have any.
>
> >
> > diff --git a/drivers/input/mouse/synaptics.c b/drivers/input/mouse/synaptics.c
> > index a039cb7..1250a5d 100644
> > --- a/drivers/input/mouse/synaptics.c
> > +++ b/drivers/input/mouse/synaptics.c
> > @@ -608,6 +608,18 @@ static void synaptics_parse_agm(const unsigned char buf[],
> > }
> > }
> >
> > +static void synaptics_parse_ext_buttons(const unsigned char buf[],
> > + struct synaptics_data *priv,
> > + struct synaptics_hw_state *hw)
> > +{
> > + unsigned int ext_bits =
> > + (SYN_CAP_MULTI_BUTTON_NO(priv->ext_cap) + 1) >> 1;
> > + unsigned int ext_mask = GENMASK(ext_bits - 1, 0);
> > +
> > + hw->ext_buttons = buf[4] & ext_mask;
> > + hw->ext_buttons |= (buf[4] & ext_mask) << ext_bits;
>
> typo: this should read (buf[5] & ext_mask) << ext_bits; (not buf[4])
Ah, yes, indeed! Thanks for spotting this.
>
> You can add my Tested-by on this one when applying.
Great, I'll queue it then.
>
> Cheers,
> Benjamin
>
> > +}
> > +
> > static int synaptics_parse_hw_state(const unsigned char buf[],
> > struct synaptics_data *priv,
> > struct synaptics_hw_state *hw)
> > @@ -692,28 +704,9 @@ static int synaptics_parse_hw_state(const unsigned char buf[],
> > hw->down = ((buf[0] ^ buf[3]) & 0x02) ? 1 : 0;
> > }
> >
> > - if (SYN_CAP_MULTI_BUTTON_NO(priv->ext_cap) &&
> > + if (SYN_CAP_MULTI_BUTTON_NO(priv->ext_cap) > 0 &&
> > ((buf[0] ^ buf[3]) & 0x02)) {
> > - switch (SYN_CAP_MULTI_BUTTON_NO(priv->ext_cap) & ~0x01) {
> > - default:
> > - /*
> > - * if nExtBtn is greater than 8 it should be
> > - * considered invalid and treated as 0
> > - */
> > - break;
> > - case 8:
> > - hw->ext_buttons |= ((buf[5] & 0x08)) ? 0x80 : 0;
> > - hw->ext_buttons |= ((buf[4] & 0x08)) ? 0x40 : 0;
> > - case 6:
> > - hw->ext_buttons |= ((buf[5] & 0x04)) ? 0x20 : 0;
> > - hw->ext_buttons |= ((buf[4] & 0x04)) ? 0x10 : 0;
> > - case 4:
> > - hw->ext_buttons |= ((buf[5] & 0x02)) ? 0x08 : 0;
> > - hw->ext_buttons |= ((buf[4] & 0x02)) ? 0x04 : 0;
> > - case 2:
> > - hw->ext_buttons |= ((buf[5] & 0x01)) ? 0x02 : 0;
> > - hw->ext_buttons |= ((buf[4] & 0x01)) ? 0x01 : 0;
> > - }
> > + synaptics_parse_ext_buttons(buf, priv, hw);
> > }
> > } else {
> > hw->x = (((buf[1] & 0x1f) << 8) | buf[2]);
> > @@ -780,6 +773,7 @@ static void synaptics_report_buttons(struct psmouse *psmouse,
> > {
> > struct input_dev *dev = psmouse->dev;
> > struct synaptics_data *priv = psmouse->private;
> > + int ext_bits = (SYN_CAP_MULTI_BUTTON_NO(priv->ext_cap) + 1) >> 1;
> > int i;
> >
> > input_report_key(dev, BTN_LEFT, hw->left);
> > @@ -793,8 +787,12 @@ static void synaptics_report_buttons(struct psmouse *psmouse,
> > input_report_key(dev, BTN_BACK, hw->down);
> > }
> >
> > - for (i = 0; i < SYN_CAP_MULTI_BUTTON_NO(priv->ext_cap); i++)
> > - input_report_key(dev, BTN_0 + i, hw->ext_buttons & (1 << i));
> > + for (i = 0; i < ext_bits; i++) {
> > + input_report_key(dev, BTN_0 + 2 * i,
> > + hw->ext_buttons & (1 << i));
> > + input_report_key(dev, BTN_1 + 2 * i,
> > + hw->ext_buttons & (1 << (i + ext_bits)));
> > + }
> > }
> >
> > static void synaptics_report_mt_data(struct psmouse *psmouse,
> >
> > Thanks.
> >
> > --
> > Dmitry
--
Dmitry
next prev parent reply other threads:[~2015-02-04 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 20:10 [PATCH 0/4] New Lenovos 2015 touchpads: party time! Benjamin Tissoires
2015-01-28 20:10 ` [PATCH 1/4] Input - synaptics: fix middle button on Lenovo 2015 products Benjamin Tissoires
2015-02-02 22:54 ` Dmitry Torokhov
2015-02-04 19:43 ` Benjamin Tissoires
2015-02-04 19:53 ` Dmitry Torokhov [this message]
2015-01-28 20:10 ` [PATCH 2/4] Input - synaptics: do not release extra buttons once they are pressed Benjamin Tissoires
2015-02-02 21:46 ` Dmitry Torokhov
2015-02-02 22:14 ` Benjamin Tissoires
2015-02-04 21:29 ` Benjamin Tissoires
2015-02-05 1:53 ` Andrew Duggan
2015-02-06 1:54 ` Andrew Duggan
2015-01-28 20:10 ` [PATCH 3/4] Input - synaptics: remove TOPBUTTONPAD property for Lenovos 2015 Benjamin Tissoires
2015-02-02 21:59 ` Dmitry Torokhov
2015-01-28 20:10 ` [PATCH 4/4] Input - synaptics: Remove X1 Carbon 3rd gen from the topbuttonpad list Benjamin Tissoires
2015-01-29 7:52 ` [PATCH 0/4] New Lenovos 2015 touchpads: party time! Hans de Goede
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=20150204195359.GD15782@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=hdegoede@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
/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).