From: Benjamin Gaignard <benjamin.gaignard@st.com>
To: <linus.walleij@linaro.org>, <alexandre.torgue@st.com>,
<amelie.delaunay@st.com>
Cc: Benjamin Gaignard <benjamin.gaignard@st.com>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
benjamin.gaignard@linaro.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Allow pinctrl framework to create links
Date: Wed, 22 May 2019 17:29:23 +0200 [thread overview]
Message-ID: <20190522152925.12419-1-benjamin.gaignard@st.com> (raw)
Some pin controllers may need to ensure suspend/resume calls ordering between
themselves and their clients.
That is the case for STMFX (an I2C GPIO expender) which need to be suspended
after all it clients to let them call pinctrl_pm_select_sleep_state() before
perform it own suspend function. It is the same problem for resume but in
reverse order.
This series allow to let pinctrl core knows if a controller would like to
create link between itself and it client by setting create_link to true.
Benjamin Gaignard (2):
pinctrl: Allow to create link between controller and consumer
pinctrl: stmfx: enable links creations
drivers/pinctrl/core.c | 11 +++++++++++
drivers/pinctrl/pinctrl-stmfx.c | 1 +
include/linux/pinctrl/pinctrl.h | 2 ++
3 files changed, 14 insertions(+)
--
2.15.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-05-22 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 15:29 Benjamin Gaignard [this message]
2019-05-22 15:29 ` [PATCH 1/2] pinctrl: Allow to create link between controller and consumer Benjamin Gaignard
2019-05-22 15:29 ` [PATCH 2/2] pinctrl: stmfx: enable links creations Benjamin Gaignard
2019-05-23 7:37 ` [PATCH 0/2] Allow pinctrl framework to create links Linus Walleij
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=20190522152925.12419-1-benjamin.gaignard@st.com \
--to=benjamin.gaignard@st.com \
--cc=alexandre.torgue@st.com \
--cc=amelie.delaunay@st.com \
--cc=benjamin.gaignard@linaro.org \
--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 \
/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).