From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Daniel Drake <drake@endlessm.com>
Cc: Chris Chiu <chiu@endlessm.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
"open list:PIN CONTROL SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Upstreaming Team <linux@endlessm.com>,
Andy Shevchenko <andriy.shevchenko@intel.com>
Subject: Re: [PATCH] pinctrl: intel: save HOSTSW_OWN register over suspend/resume
Date: Thu, 28 Mar 2019 10:28:24 +0200 [thread overview]
Message-ID: <20190328082824.GU3622@lahna.fi.intel.com> (raw)
In-Reply-To: <20190327172940.GR3622@lahna.fi.intel.com>
On Wed, Mar 27, 2019 at 07:29:40PM +0200, Mika Westerberg wrote:
> I wonder if it would be simpler to save it always and then upon resume
> compare them and if changed, log this in dmesg and restore the saved
> one.
Actually I think better is to restore hostsw_own only for GPIOs that are
already requested by us. The BIOS should have no business messing those
anyway once they are owned by the GPIO driver.
next prev parent reply other threads:[~2019-03-28 8:28 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 10:41 [PATCH] pinctrl: intel: save HOSTSW_OWN register over suspend/resume Chris Chiu
[not found] ` <20171115080446.GY17200@lahna.fi.intel.com>
2017-11-15 8:08 ` Chris Chiu
2017-11-15 10:13 ` Mika Westerberg
2017-11-15 10:19 ` Chris Chiu
2017-11-16 12:44 ` Mika Westerberg
2017-11-16 13:27 ` Chris Chiu
2017-11-17 6:49 ` Mika Westerberg
2017-11-17 8:11 ` Chris Chiu
2017-11-21 10:52 ` Mika Westerberg
2017-11-21 11:54 ` Chris Chiu
2017-11-21 12:04 ` Mika Westerberg
2017-11-23 12:24 ` Chris Chiu
2017-11-23 12:43 ` Mika Westerberg
2019-03-27 8:22 ` Daniel Drake
2019-03-27 17:29 ` Mika Westerberg
2019-03-28 8:28 ` Mika Westerberg [this message]
2019-03-28 9:17 ` Andy Shevchenko
2019-03-28 9:38 ` Daniel Drake
2019-03-28 12:19 ` Chris Chiu
2019-03-28 12:34 ` Mika Westerberg
2019-03-29 8:38 ` Chris Chiu
2019-04-01 7:49 ` Mika Westerberg
2019-04-01 10:41 ` Chris Chiu
2019-04-01 12:22 ` Andy Shevchenko
2019-04-02 6:16 ` Chris Chiu
2019-04-02 11:58 ` Andy Shevchenko
2019-04-03 7:06 ` Chris Chiu
2019-04-03 13:06 ` Andy Shevchenko
2019-04-04 13:06 ` Chris Chiu
2019-04-04 13:59 ` 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=20190328082824.GU3622@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.