From: 'Dmitry Torokhov' <dmitry.torokhov@gmail.com>
To: 廖崇榮 <kt.liao@emc.com.tw>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
ulrik.debie-os@e2big.org, phoenix@emc.com.tw,
aaron.ma@canonical.com, josh.chen@emc.com.tw
Subject: Re: [PATCH] Input: elantech - Fix V4 report decoding for module with middle key
Date: Thu, 21 Jun 2018 17:16:32 -0700 [thread overview]
Message-ID: <20180622001632.GI79890@dtor-ws> (raw)
In-Reply-To: <000301d3f7e4$5c9e51c0$15daf540$@emc.com.tw>
On Wed, May 30, 2018 at 03:03:50PM +0800, 廖崇榮 wrote:
> Hi Dmitry,
>
> -----Original Message-----
> From: Dmitry Torokhov [mailto:dmitry.torokhov@gmail.com]
> Sent: Wednesday, May 30, 2018 2:05 AM
> To: KT Liao
> Cc: linux-kernel@vger.kernel.org; linux-input@vger.kernel.org;
> ulrik.debie-os@e2big.org; phoenix@emc.com.tw; aaron.ma@canonical.com;
> josh.chen@emc.com.tw
> Subject: Re: [PATCH] Input: elantech - Fix V4 report decoding for module
> with middle key
>
> Hi KT,
>
> On Mon, May 28, 2018 at 07:33:02PM +0800, KT Liao wrote:
> > Some touchpad has middle key and it will be indicated in bit 2 of
> packet[0].
> > We need to fix V4 formation's byte mask to prevent error decoding.
>
> Could you please let me know what devices this patch fixes? Are they
> released or new hardware?
>
>
> The primary target is Lenovo thinkpad P52 and it will be released in 6/M.
>
> force_crc_enabled will fix the issue too because less bit-check in the
> specific byte.
> I guess Fujitsu H730/H760 in elantech_dmi_force_crc_enabled may have the
> same issue.
> I leave them in DMI table because I am not sure of it.
OK, thank you for the info. Applied.
>
> Thanks
> KT
> >
> > Signed-off-by: KT Liao <kt.liao@emc.com.tw>
> > ---
> > drivers/input/mouse/elantech.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/input/mouse/elantech.c
> > b/drivers/input/mouse/elantech.c index fb4d902..f39dc66 100644
> > --- a/drivers/input/mouse/elantech.c
> > +++ b/drivers/input/mouse/elantech.c
> > @@ -799,7 +799,7 @@ static int elantech_packet_check_v4(struct psmouse
> *psmouse)
> > else if (ic_version == 7 && etd->info.samples[1] == 0x2A)
> > sanity_check = ((packet[3] & 0x1c) == 0x10);
> > else
> > - sanity_check = ((packet[0] & 0x0c) == 0x04 &&
> > + sanity_check = ((packet[0] & 0x08) == 0x00 &&
> > (packet[3] & 0x1c) == 0x10);
> >
> > if (!sanity_check)
> > --
> > 2.7.4
> >
>
> Thanks.
>
> --
> Dmitry
>
--
Dmitry
next prev parent reply other threads:[~2018-06-22 0:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 11:33 [PATCH] Input: elantech - Fix V4 report decoding for module with middle key KT Liao
2018-05-29 18:05 ` Dmitry Torokhov
2018-05-30 7:03 ` 廖崇榮
2018-06-22 0:16 ` 'Dmitry Torokhov' [this message]
2018-07-01 23:30 ` Linus Torvalds
2018-07-01 23:44 ` Dmitry Torokhov
2018-07-02 0:00 ` Linus Torvalds
2018-07-02 0:12 ` Dmitry Torokhov
2018-07-02 12:12 ` Kalle Valo
2018-07-02 15:32 ` Randy Dunlap
2018-07-02 16:31 ` Linus Torvalds
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=20180622001632.GI79890@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=aaron.ma@canonical.com \
--cc=josh.chen@emc.com.tw \
--cc=kt.liao@emc.com.tw \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phoenix@emc.com.tw \
--cc=ulrik.debie-os@e2big.org \
/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).