From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Nish Aravamudan <nish.aravamudan@gmail.com>,
Jiri Kosina <jikos@kernel.org>,
Andrew Duggan <aduggan@synaptics.com>,
Gabriele Mazzotta <gabriele.mzt@gmail.com>,
Seth Forshee <seth.forshee@canonical.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
linux-input@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RESEND] Lenovo Yoga 900 touchpad issues
Date: Mon, 21 Dec 2015 13:32:47 +0200 [thread overview]
Message-ID: <20151221113247.GB1758@lahna.fi.intel.com> (raw)
In-Reply-To: <20151218161031.GB12730@mail.corp.redhat.com>
On Fri, Dec 18, 2015 at 05:10:31PM +0100, Benjamin Tissoires wrote:
> After turning this around, I think I finally got what was going on (and
> yes, it's basically a race that should have been caught long ago):
> - during resume, the i2c-hid driver calls reset, which is a long (few
> ms) operation.
> - hid-multitouch is also called during resume, and right after i2c-hid
> - hid-multiotuch immediately emits for touchpads a set input mode (this
> was unseen with touchscreens because they do not have to be switched
> into a proper mode)
> - there is a race between hid-multitouch accessing the features while
> the device is still resetting. And our reset interrupt never gets to
> us because there was an other operation in progress to request/set
> reports
>
> So the actual fix would be to make hid-multitouch wait until we reset
> i2c-hid.
The driver used for touchpad is actually hid-rmi but you are right, it
tries to set rmi mode (or something) during its rmi_post_reset() that
then confuses the i2c-hid driver.
Thanks for the analysis :-)
> This should be done by either a mutex or a spinlock in
> i2c_hid_output_raw_report() and i2c_hid_resume() that would protect a
> flag set during suspend and cleared after resume.
Makes sense. I'll make a patch that does this and submit it soon.
next prev parent reply other threads:[~2015-12-21 11:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 19:14 Nish Aravamudan
2015-12-16 9:28 ` Mika Westerberg
2015-12-16 13:18 ` Jiri Kosina
2015-12-16 22:59 ` Nish Aravamudan
2015-12-17 9:53 ` Benjamin Tissoires
2015-12-17 16:48 ` Nish Aravamudan
2015-12-17 17:28 ` Benjamin Tissoires
2015-12-17 17:34 ` Nish Aravamudan
2015-12-16 22:58 ` Nish Aravamudan
2015-12-18 14:42 ` Mika Westerberg
2015-12-18 15:38 ` Mika Westerberg
2015-12-18 16:10 ` Benjamin Tissoires
2015-12-21 11:32 ` Mika Westerberg [this message]
2015-12-18 17:54 ` Nish Aravamudan
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=20151221113247.GB1758@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=aduggan@synaptics.com \
--cc=benjamin.tissoires@redhat.com \
--cc=dan.carpenter@oracle.com \
--cc=gabriele.mzt@gmail.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nish.aravamudan@gmail.com \
--cc=seth.forshee@canonical.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
Powered by JetHome