From: Florian Fainelli <f.fainelli@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linus.walleij@linaro.org, swarren@nvidia.com,
andy.shevchenko@gmail.com, alcooperx@gmail.com,
linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, mark.rutland@arm.com,
bcm-kernel-feedback-list@broadcom.com,
Florian Fainelli <f.fainelli@gmail.com>
Subject: [PATCH 0/2] pinctrl: Allow indicating loss of state across suspend/resume
Date: Wed, 20 Sep 2017 18:04:19 -0700 [thread overview]
Message-ID: <20170921010421.7467-1-f.fainelli@gmail.com> (raw)
Hello Linus,
It's me again, so I have been thinking about the problem originally
reported in: [PATCH fixes v3] pinctrl: Really force states during suspend/resume
and other similar patches a while ago, and this new version allows a platform
using pinctrl-single to specify whether its pins are going to lose their state
during a system deep sleep.
Note that this is still checked at the pinctrl_select_state() because consumers
of the pinctrl API might be calling this from their suspend/resume functions
and should not have to know whether the provider does lose its pin states.
Thanks!
Florian Fainelli (2):
pinctrl: Allow a device to indicate when to force a state
pinctrl: single: Allow indicating loss of pin states during low-power
.../devicetree/bindings/pinctrl/pinctrl-single.txt | 4 ++++
drivers/pinctrl/core.c | 15 +++++++++++++++
drivers/pinctrl/core.h | 4 ++++
drivers/pinctrl/pinctrl-single.c | 3 +++
4 files changed, 26 insertions(+)
--
2.14.1
next reply other threads:[~2017-09-21 1:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 1:04 Florian Fainelli [this message]
2017-09-21 1:04 ` [PATCH 1/2] pinctrl: Allow a device to indicate when to force a state Florian Fainelli
2017-09-22 11:55 ` Linus Walleij
2017-09-22 13:20 ` Charles Keepax
2017-09-22 13:57 ` Linus Walleij
2017-09-25 19:18 ` Florian Fainelli
[not found] ` <20170922132011.wssbhnsggteffgte-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2017-09-22 16:57 ` Florian Fainelli
2017-09-26 14:16 ` Charles Keepax
2017-09-26 17:51 ` Florian Fainelli
2017-09-27 8:26 ` Charles Keepax
2017-09-22 12:47 ` Charles Keepax
2017-09-22 16:45 ` Florian Fainelli
2017-09-21 1:04 ` [PATCH 2/2] pinctrl: single: Allow indicating loss of pin states during low-power Florian Fainelli
[not found] ` <20170921010421.7467-3-f.fainelli-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-09-22 13:03 ` Linus Walleij
2017-09-25 19:15 ` Florian Fainelli
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=20170921010421.7467-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=alcooperx@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=swarren@nvidia.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).