From: Benjamin GAIGNARD <benjamin.gaignard@st.com>
To: "broonie@kernel.org" <broonie@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"arnd@arndb.de" <arnd@arndb.de>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"fabio.estevam@nxp.com" <fabio.estevam@nxp.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Loic PALLARDY" <loic.pallardy@st.com>,
"benjamin.gaignard@linaro.org" <benjamin.gaignard@linaro.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"linux-imx@nxp.com" <linux-imx@nxp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Subject: Re: [RESEND PATCH 1/7] devicetree: bindings: Document domains controller bindings
Date: Mon, 29 Apr 2019 08:49:39 +0000 [thread overview]
Message-ID: <dbb7440f-f055-6ff3-d367-3435c3c34d89@st.com> (raw)
In-Reply-To: <20190318100605.29120-2-benjamin.gaignard@st.com>
On 3/18/19 11:05 AM, Benjamin Gaignard wrote:
> Document commons domains controller bindings for controller
> and client devices.
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
Hi Rob,
In the first version of this series you have asked me to rework the
framework description.
Does this v2 feel better for you ?
Benjamin
> ---
> .../bindings/bus/domains/domainsctrl.txt | 55 ++++++++++++++++++++++
> 1 file changed, 55 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/bus/domains/domainsctrl.txt
>
> diff --git a/Documentation/devicetree/bindings/bus/domains/domainsctrl.txt b/Documentation/devicetree/bindings/bus/domains/domainsctrl.txt
> new file mode 100644
> index 000000000000..f82e5e11ea64
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/bus/domains/domainsctrl.txt
> @@ -0,0 +1,55 @@
> +Common Domains Controller bindings properties
> +
> +Bus domains controllers allow to divided system on chip into multiple domains
> +that can be used to select by who hardware blocks could be accessed.
> +A domain could be a cluster of CPUs (or coprocessors), a range of addresses or
> +a group of hardware blocks.
> +
> +This device tree bindings can be used to bind bus domain consumer devices with
> +their bus domains provided by bus domains controllers. A bus domain provider
> +can be represented by any node in the device tree and can provide one or more
> +bus domains. A consumer node can refer to the provider by a phandle and a set
> +of phandle arguments of length specified by the #domainctrl-cells property in
> +the bus domain provider node.
> +
> +==Bus domain provider==
> +
> +Required properties:
> +- #domainctrl-cells : Number of cells in a bus domain specifier;
> + Can be any value as specified by device tree binding
> + documentation of a particular provider.
> +
> +==Bus domain consumer==
> +
> +Required properties:
> +- domainsctrl-X : A list of bus domain specifiers, as defined by
> + bindings of the bus domain controller that is the
> + bus domain provider.
> +
> +Optional properties:
> +- domainsctrl-names : A list of bus domain name string sorted in the same
> + order as the domainsctrl-X proprerties. Consumer
> + drivers will use domainsctrl-names to match bus
> + domains with bus domains specifiers.
> + Note that "default" and "unbind" are reserved names
> + used by the framework.
> +
> +Example of usage with:
> +- a domains controller with a 2 parameters cell
> +- a domains controller with a 3 parameters cell
> +- a client device node using the both controllers and 2 configurations
> + named "default" and "unbind"
> +
> +ctrl0: ctrl@0 {
> + #domainctrl-cells = <2>;
> +};
> +
> +ctrl1: ctrl@1 {
> + #domainctrl-cells = <3>;
> +};
> +
> +foo@0 {
> + domains-names = "default", "unbind";
> + domainctrl-0 = <&ctrl0 1 2>, <&ctrl1 3 4 5>;
> + domainctrl-1 = <&ctrl0 6 7>, <&ctrl1 8 9 0>;
> +};
next prev parent reply other threads:[~2019-04-29 8:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 10:05 [RESEND PATCH 0/7] Introduce bus domains controller framework Benjamin Gaignard
2019-03-18 10:05 ` [RESEND PATCH 1/7] devicetree: bindings: Document domains controller bindings Benjamin Gaignard
2019-04-29 8:49 ` Benjamin GAIGNARD [this message]
2019-03-18 10:06 ` [RESEND PATCH 2/7] domainsctrl: Introduce domains controller framework Benjamin Gaignard
2019-03-18 10:06 ` [RESEND PATCH 3/7] base: Add calls to domains controller Benjamin Gaignard
2019-03-18 10:06 ` [RESEND PATCH 4/7] devicetree: bindings: domainsctrl: Add STM32 ETZPC bindings Benjamin Gaignard
2019-03-18 10:06 ` [RESEND PATCH 5/7] bus: domainsctrl: Add driver for STM32 ETZPC controller Benjamin Gaignard
2019-03-18 10:06 ` [RESEND PATCH 6/7] ARM: dts: stm32: Add domainsctrl node for stm32mp157 SoC Benjamin Gaignard
2019-03-18 10:06 ` [RESEND PATCH 7/7] ARM: dts: stm32: enable domains controller node on stm32mp157c-ed1 Benjamin Gaignard
2019-03-18 10:43 ` [RESEND PATCH 0/7] Introduce bus domains controller framework Sudeep Holla
2019-03-18 11:05 ` Benjamin Gaignard
2019-04-19 12:36 ` Benjamin Gaignard
2019-04-23 7:41 ` Enrico Weigelt, metux IT consult
2019-04-23 13:21 ` Sudeep Holla
2019-04-23 13:33 ` Benjamin GAIGNARD
2019-04-23 13:55 ` Sudeep Holla
2019-04-23 14:17 ` Benjamin GAIGNARD
2019-04-25 18:01 ` Mark Brown
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=dbb7440f-f055-6ff3-d367-3435c3c34d89@st.com \
--to=benjamin.gaignard@st.com \
--cc=arnd@arndb.de \
--cc=benjamin.gaignard@linaro.org \
--cc=broonie@kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=gregkh@linuxfoundation.org \
--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®