From: Laura Abbott <labbott@redhat.com>
To: Paul Donohue <linux-kernel@PaulSD.com>
Cc: Masaki Ota <masaki.ota@jp.alps.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Pali Rohar <pali.rohar@gmail.com>,
Nick Fletcher <nick.m.fletcher@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
scott.s.lowe@gmail.com
Subject: Re: [REGRESSION] Touchpad failure after e7348396c6d5 ("Input: ALPS - fix V8+ protocol handling (73 03 28)")
Date: Tue, 6 Jun 2017 09:59:11 -0700 [thread overview]
Message-ID: <e841f28c-4d63-170a-482f-8ef1deda1900@redhat.com> (raw)
In-Reply-To: <20170603040349.GB16345@TopQuark.net>
On 06/02/2017 09:03 PM, Paul Donohue wrote:
> This might be related to https://bugzilla.kernel.org/show_bug.cgi?id=195215
>
> Could you have the user try this change? https://bugzilla.kernel.org/show_bug.cgi?id=195215#c12
>
https://bugzilla.redhat.com/show_bug.cgi?id=1447327#c13
"Cursor movement seems to work, but there are intermittent two-finger scrolling
issues on the right-hand side of the touchpad. There are no issues with cursor
movement or two-finger scrolling on the left-hand side of the touchpad."
> On Fri, Jun 02, 2017 at 10:54:52AM -0700, Laura Abbott wrote:
>> Hi,
>>
>> Fedora got a bug report https://bugzilla.redhat.com/show_bug.cgi?id=1447327
>> of a touchpad failure on a Dell Latitude E7370. Testing showed that the
>> bad commit was
>>
>> commit e7348396c6d51b57c95c6646c390cd078e038e19
>> Author: Masaki Ota <masaki.ota@jp.alps.com>
>> Date: Fri Mar 17 14:10:57 2017 -0700
>>
>> Input: ALPS - fix V8+ protocol handling (73 03 28)
>>
>> Devices identified as E7="73 03 28" use slightly modified version of V8
>> protocol, with lower count per electrode, different offsets, and different
>> feature bits in OTP data.
>>
>> Fixes: aeaa881f9b17 ("Input: ALPS - set DualPoint flag for 74 03 28 devices")
>> Signed-off-by: Masaki Ota <masaki.ota@jp.alps.com>
>> Acked-by: Pali Rohar <pali.rohar@gmail.com>
>> Tested-by: Paul Donohue <linux-kernel@PaulSD.com>
>> Tested-by: Nick Fletcher <nick.m.fletcher@gmail.com>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
>>
>> I suspect this particular model needs special handling as well?
>>
>> Thanks,
>> Laura
>>
next prev parent reply other threads:[~2017-06-06 16:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 17:54 [REGRESSION] Touchpad failure after e7348396c6d5 ("Input: ALPS - fix V8+ protocol handling (73 03 28)") Laura Abbott
2017-06-03 4:03 ` Paul Donohue
2017-06-06 16:59 ` Laura Abbott [this message]
2017-06-12 5:25 ` Masaki Ota
2017-06-14 18:52 ` Laura Abbott
2017-06-15 0:33 ` Masaki Ota
2017-06-19 18:43 ` Paul Donohue
2017-06-19 20:02 ` Laura Abbott
2017-06-19 23:20 ` Paul Donohue
2017-07-11 15:50 ` Takashi Iwai
2017-07-11 19:58 ` Paul Donohue
2017-07-12 7:16 ` Takashi Iwai
2017-07-12 16:28 ` Paul Donohue
2017-07-19 8:57 ` Takashi Iwai
2017-07-20 9:20 ` Masaki Ota
2017-07-20 9:35 ` Takashi Iwai
2017-07-20 10:02 ` Masaki Ota
2017-07-20 10:43 ` Takashi Iwai
2017-07-22 18:57 ` Paul Donohue
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=e841f28c-4d63-170a-482f-8ef1deda1900@redhat.com \
--to=labbott@redhat.com \
--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=nick.m.fletcher@gmail.com \
--cc=pali.rohar@gmail.com \
--cc=scott.s.lowe@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;
as well as URLs for NNTP newsgroup(s).