From: Mark Brown <broonie@kernel.org>
To: Benjamin Gaignard <benjamin.gaignard@st.com>
Cc: robh@kernel.org, arnd@arndb.de, shawnguo@kernel.org,
s.hauer@pengutronix.de, fabio.estevam@nxp.com,
linux-kernel@vger.kernel.org, loic.pallardy@st.com,
benjamin.gaignard@linaro.org, kernel@pengutronix.de,
linux-imx@nxp.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC v2 3/7] base: Add calls to domains controller
Date: Tue, 29 Jan 2019 15:14:12 +0000 [thread overview]
Message-ID: <20190129151412.GE10524@sirena.org.uk> (raw)
In-Reply-To: <20190128142313.17036-4-benjamin.gaignard@st.com>
[-- Attachment #1: Type: text/plain, Size: 259 bytes --]
On Mon, Jan 28, 2019 at 03:23:09PM +0100, Benjamin Gaignard wrote:
> To avoid modifying all the drivers call domainsctrl_set_default_config
> before probe to apply the configuration define in device node (if any).
Reviwed-by: Mark Brown <broonie@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-29 15:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 14:23 [RFC v2 0/7] Introduce bus domains controller framework Benjamin Gaignard
2019-01-28 14:23 ` [RFC v2 1/7] devicetree: bindings: Document domains controller bindings Benjamin Gaignard
2019-02-18 16:04 ` Benjamin Gaignard
2019-01-28 14:23 ` [RFC v2 2/7] domainsctrl: Introduce domains controller framework Benjamin Gaignard
2019-01-29 15:12 ` Mark Brown
2019-01-28 14:23 ` [RFC v2 3/7] base: Add calls to domains controller Benjamin Gaignard
2019-01-29 15:14 ` Mark Brown [this message]
2019-01-28 14:23 ` [RFC v2 4/7] devicetree: bindings: domainsctrl: Add STM32 ETZPC bindings Benjamin Gaignard
2019-01-28 14:23 ` [RFC v2 5/7] bus: domainsctrl: Add driver for STM32 ETZPC controller Benjamin Gaignard
2019-01-28 14:23 ` [RFC v2 6/7] ARM: dts: stm32: Add domainsctrl node for stm32mp157 SoC Benjamin Gaignard
2019-01-28 14:23 ` [RFC v2 7/7] ARM: dts: stm32: enable domains controller node on stm32mp157c-ed1 Benjamin Gaignard
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=20190129151412.GE10524@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=benjamin.gaignard@linaro.org \
--cc=benjamin.gaignard@st.com \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.pallardy@st.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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®