From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Benjamin Tissoires <btissoir@redhat.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Jiri Kosina <jikos@kernel.org>, Jingoo Han <jingoohan1@gmail.com>,
Pratyush Anand <pratyush.anand@gmail.com>
Subject: Re: hid-multitouch stuck taps, possibly 4.5 regression?
Date: Thu, 17 Mar 2016 10:06:12 +0200 [thread overview]
Message-ID: <20160317080612.GN1793@lahna.fi.intel.com> (raw)
In-Reply-To: <CALCETrWRi8nM6h234ppeQZ3VaAqL4d37VmZvt6HSYwDYddO3Kw@mail.gmail.com>
On Wed, Mar 16, 2016 at 02:59:48PM -0700, Andy Lutomirski wrote:
> [add i2c-designware maintainers]
>
> On Wed, Mar 16, 2016 at 1:47 AM, Benjamin Tissoires <btissoir@redhat.com> wrote:
> > Hi Andy,
> >
> > On Mar 15 2016 or thereabouts, Andy Lutomirski wrote:
> >> Hi-
> >>
> >> In 4.5 and several 4.5 rcs, I see occasional stuck taps (I think) on
> >> my XPS 13 9350's touchpad. The effect is that trying to left-click
> >> ends up middle-clicking. I think it's a kernel issue and not a
> >> hardware or libinput issue, but I'm not 100% sure. I don't think I
> >> had this issue in 4.4.
> >>
> >> I've attached what I think is an evtest issue of my fixing the issue
> >> by pressing three fingers down in sequence and then releasing them.
> >> After doing that, left-clicks worked.
> >
> > I think I already have been reported the issue here:
> > https://bugs.freedesktop.org/show_bug.cgi?id=93948
> >
> > The result was that it was more likely an I2C transport bug than a
> > hid-multitouch one (see comment #8 in the fdo bug).
> >
> > You can try to run hid-recorder when you see the problems, and then
> > parse the output (or just send it to me). There is huge chances that
> > there will be no events from I2C sending the release.
> >
> > And again, I am not sure how we could end up debugging this in the
> > i2c-designware driver :(
> >
>
> Does this ring a bell?
i2c-designware usually prints errors to dmesg if it fails to transfer
messages. Can you include dmesg of the failure as well?
next prev parent reply other threads:[~2016-03-17 8:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 21:47 hid-multitouch stuck taps, possibly 4.5 regression? Andy Lutomirski
2016-03-16 8:47 ` Benjamin Tissoires
2016-03-16 21:59 ` Andy Lutomirski
2016-03-17 8:06 ` Mika Westerberg [this message]
2016-03-17 18:43 ` Andy Lutomirski
2016-03-17 20:24 ` Andrew Duggan
2016-03-18 17:42 ` Andy Lutomirski
2016-03-18 18:53 ` Andrew Duggan
2016-04-22 16:37 ` Andy Lutomirski
2016-06-26 23:37 ` Andy Lutomirski
2016-06-27 4:11 ` Andy Lutomirski
2016-06-27 7:47 ` Benjamin Tissoires
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=20160317080612.GN1793@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=btissoir@redhat.com \
--cc=jikos@kernel.org \
--cc=jingoohan1@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=pratyush.anand@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).