From: Andriy Shevchenko <andriy.shevchenko@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Chris Chiu <chiu@endlessm.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Daniel Drake <drake@endlessm.com>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux@endlessm.com
Subject: Re: [PATCH v3] pinctrl:intel: Retain HOSTSW_OWN for requested gpio pin
Date: Fri, 26 Apr 2019 15:50:31 +0300 [thread overview]
Message-ID: <20190426125031.GQ9224@smile.fi.intel.com> (raw)
In-Reply-To: <CACRpkdanhW206AEj7m+2FQBhJ5epUzw60Y6v+k-eoJLLW_-SSQ@mail.gmail.com>
On Tue, Apr 23, 2019 at 12:38:17PM +0200, Linus Walleij wrote:
> On Mon, Apr 15, 2019 at 7:54 AM Chris Chiu <chiu@endlessm.com> wrote:
>
> > The touchpad of the ASUS laptops E403NA, X540NA, X541NA are not
> > responsive after suspend/resume. The following error message
> > shows after resume.
> > i2c_hid i2c-ELAN1200:00: failed to reset device.
> >
> > On these laptops, the touchpad interrupt is connected via a GPIO
> > pin which is controlled by Intel pinctrl. After system resumes,
> > the GPIO is in ACPI mode and no longer works as an IRQ.
> >
> > This commit saves the HOSTSW_OWN value during suspend, make sure
> > the HOSTSW_OWN mode remains the same after resume.
> >
> > Signed-off-by: Chris Chiu <chiu@endlessm.com>
>
> This v3 patch applied with Mika's ACK.
Hmm... It's supposed to go along with our PR.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-04-26 12:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 5:53 Chris Chiu
2019-04-15 19:25 ` Mika Westerberg
2019-04-23 10:38 ` Linus Walleij
2019-04-26 12:50 ` Andriy Shevchenko [this message]
2019-04-29 18:12 ` Chris Chiu
2019-04-30 11:37 ` Andy Shevchenko
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=20190426125031.GQ9224@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=chiu@endlessm.com \
--cc=drake@endlessm.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@endlessm.com \
--cc=mika.westerberg@linux.intel.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
all inboxes | Powered by JetHome®