From: Takashi Iwai <tiwai@suse.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
"Masaki Ota" <masaki.ota@jp.alps.com>,
"Paul Donohue" <linux-kernel@PaulSD.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] Input: ALPS - Fix two-finger scroll breakage in right side on ALPS touchpad
Date: Fri, 25 Aug 2017 10:37:31 +0200 [thread overview]
Message-ID: <s5hefs0hwl0.wl-tiwai@suse.de> (raw)
In-Reply-To: <20170824230955.GB22810@dtor-ws>
On Fri, 25 Aug 2017 01:09:55 +0200,
Dmitry Torokhov wrote:
>
> Hi Takashi,
>
> On Tue, Aug 22, 2017 at 10:17:00PM +0200, Takashi Iwai wrote:
> > From: Masaki Ota <masaki.ota@jp.alps.com>
> >
> > Fixed the issue that two finger scroll does not work correctly
> > on V8 protocol. The cause is that V8 protocol X-coordinate decode
> > is wrong at SS4 PLUS device. I added SS4 PLUS X decode definition.
> >
> > Mote notes:
> > the problem manifests itself by the commit e7348396c6d5 ("Input: ALPS
> > - fix V8+ protocol handling (73 03 28)"), where a fix for the V8+
> > protocol was applied. Although the culprit must have been present
> > beforehand, the two-finger scroll worked casually even with the
> > wrongly reported values by some reason. It got broken by the commit
> > above just because it changed x_max value, and this made libinput
> > correctly figuring the MT events. Since the X coord is reported as
> > falsely doubled, the events on the right-half side go outside the
> > boundary, thus they are no longer handled. This resulted as a broken
> > two-finger scroll.
> >
> > One finger event is decoded differently, and it didn't suffer from
> > this problem. The problem was only about MT events. --tiwai
> >
> > Fixes: e7348396c6d5 ("Input: ALPS - fix V8+ protocol handling (73 03 28)")
> > Signed-off-by: Masaki Ota <masaki.ota@jp.alps.com>
> > Tested-by: Takashi Iwai <tiwai@suse.de>
> > Tested-by: Paul Donohue <linux-kernel@PaulSD.com>
> > Cc: <stable@vger.kernel.org>
> > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> > ---
> >
> > Dmitry, I resend this patch from Ota-san, as the previous thread was
> > cursed. Since this is an annoying regression in the recent kernels,
> > could you apply this? Thanks!
>
> Sorry I checked out on this patch for a bit. It is now applied and I
> will send it Linuswards in the next day or two.
>
> Thanks!
Great, thanks!
Takashi
prev parent reply other threads:[~2017-08-25 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 20:17 [PATCH RESEND] Input: ALPS - Fix two-finger scroll breakage in right side on ALPS touchpad Takashi Iwai
2017-08-24 23:09 ` Dmitry Torokhov
2017-08-25 8:37 ` Takashi Iwai [this message]
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=s5hefs0hwl0.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@PaulSD.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masaki.ota@jp.alps.com \
--cc=pali.rohar@gmail.com \
/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