From: Rob Herring <robh@kernel.org>
To: Benjamin Gaignard <benjamin.gaignard@st.com>
Cc: mcoquelin.stm32@gmail.com, alexandre.torgue@st.com,
linus.walleij@linaro.org, gregkh@linuxfoundation.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stefano.stabellini@xilinx.com,
tomase@xilinx.com, devicetree@vger.kernel.org
Subject: Re: [PATCH v4 3/5] dt-bindings: bus: Add STM32 ETZPC firewall controller
Date: Mon, 13 Jul 2020 11:05:42 -0600 [thread overview]
Message-ID: <20200713170542.GA384390@bogus> (raw)
In-Reply-To: <20200701132523.32533-4-benjamin.gaignard@st.com>
On Wed, Jul 01, 2020 at 03:25:21PM +0200, Benjamin Gaignard wrote:
> Document STM32 ETZPC firewall controller bindings
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
> ---
> .../bindings/bus/stm32/st,stm32-etzpc.yaml | 46 ++++++++++++++++++++++
> 1 file changed, 46 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/bus/stm32/st,stm32-etzpc.yaml
>
> diff --git a/Documentation/devicetree/bindings/bus/stm32/st,stm32-etzpc.yaml b/Documentation/devicetree/bindings/bus/stm32/st,stm32-etzpc.yaml
> new file mode 100644
> index 000000000000..d92865fda40c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/bus/stm32/st,stm32-etzpc.yaml
> @@ -0,0 +1,46 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/bus/stm32/st,stm32-etzpc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: STM32 Extended TrustZone Protection controller
> +
> +maintainers:
> + - Benjamin Gaignard <benjamin.gaignard@st.com>
> +
> +description: STMicroelectronics's STM32 firewall bus controller implementation
> +
> +allOf:
> + - $ref: "firewall-provider.yaml#"
> + - $ref: /schemas/simple-bus.yaml#
Your bus has controls/setup, it's not a simple-bus.
Do you expect an old kernel or one with support for "st,stm32-etzpc-bus"
disabled to work? How's it going to know if certain nodes can't be
accessed without that support?
> +
> +properties:
> + compatible:
> + contains:
> + enum:
> + - st,stm32-etzpc-bus
> +
> + reg:
> + maxItems: 1
> +
> + '#firewall-cells':
> + const: 2
> +
> +required:
> + - compatible
> + - reg
> + - '#firewall-cells'
> +
> +examples:
> + - |
> + soc@5c007000 {
> + compatible = "st,stm32-etzpc-bus", "simple-bus";
> + reg = <0x5c007000 0x400>;
> + #firewall-cells = <2>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges;
> + };
> +
> +...
> --
> 2.15.0
>
next prev parent reply other threads:[~2020-07-13 17:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 13:25 [PATCH v4 0/5] STM32 ETZPC bus controller Benjamin Gaignard
2020-07-01 13:25 ` [PATCH v4 1/5] dt-bindings: bus: Add firewall bindings Benjamin Gaignard
2020-07-13 17:01 ` Rob Herring
2020-07-20 9:17 ` Benjamin GAIGNARD
2020-07-01 13:25 ` [PATCH v4 2/5] bus: stm32: Introduce firewall controller helpers Benjamin Gaignard
2020-07-01 13:25 ` [PATCH v4 3/5] dt-bindings: bus: Add STM32 ETZPC firewall controller Benjamin Gaignard
2020-07-13 17:05 ` Rob Herring [this message]
2020-07-20 9:21 ` Benjamin GAIGNARD
2020-07-01 13:25 ` [PATCH v4 4/5] bus: stm32: Add stm32 ETZPC firewall bus controller Benjamin Gaignard
2020-07-01 13:25 ` [PATCH v4 5/5] ARM: dts: stm32: Use ETZPC firewall bus 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=20200713170542.GA384390@bogus \
--to=robh@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=stefano.stabellini@xilinx.com \
--cc=tomase@xilinx.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).