From: Alexandre Torgue <alexandre.torgue@st.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-gpio@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<alexandre.torgue@st.com>
Subject: [PATCH 0/2] pinctrl: stm32: add suspend/resume management
Date: Fri, 10 May 2019 09:42:28 +0200 [thread overview]
Message-ID: <1557474150-19618-1-git-send-email-alexandre.torgue@st.com> (raw)
During power sequence, GPIO hardware registers could be lost if the power
supply is switched off. Each device using pinctrl API is in charge of
managing pins during suspend/resume sequences. But for pins used as gpio or
irq stm32 pinctrl driver has to save the hardware configuration.
Each register will be saved at runtime and restored during resume sequence.
Regards
Alex
Alexandre Torgue (2):
pinctrl: stm32: add suspend/resume management
pinctrl: stm32: Enable suspend/resume for stm32mp157c SoC
drivers/pinctrl/stm32/pinctrl-stm32.c | 132 +++++++++++++++++++++++++++++
drivers/pinctrl/stm32/pinctrl-stm32.h | 2 +
drivers/pinctrl/stm32/pinctrl-stm32mp157.c | 5 ++
3 files changed, 139 insertions(+)
--
2.7.4
next reply other threads:[~2019-05-10 7:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 7:42 Alexandre Torgue [this message]
2019-05-10 7:42 ` [PATCH 1/2] pinctrl: stm32: add suspend/resume management Alexandre Torgue
2019-05-10 7:42 ` [PATCH 2/2] pinctrl: stm32: Enable suspend/resume for stm32mp157c SoC Alexandre Torgue
2019-05-24 11:24 ` [PATCH 0/2] pinctrl: stm32: add suspend/resume management Linus Walleij
2019-05-24 12:26 ` Alexandre Torgue
2019-05-27 16:17 ` Alexandre Torgue
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=1557474150-19618-1-git-send-email-alexandre.torgue@st.com \
--to=alexandre.torgue@st.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@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).