From: Benjamin Gaignard <benjamin.gaignard@st.com>
To: <robh+dt@kernel.org>, <mcoquelin.stm32@gmail.com>,
<alexandre.torgue@st.com>, <linus.walleij@linaro.org>,
<gregkh@linuxfoundation.org>
Cc: <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>, Benjamin Gaignard <benjamin.gaignard@st.com>
Subject: [PATCH v4 3/5] dt-bindings: bus: Add STM32 ETZPC firewall controller
Date: Fri, 5 Jun 2020 10:33:46 +0200 [thread overview]
Message-ID: <20200605083348.13880-4-benjamin.gaignard@st.com> (raw)
In-Reply-To: <20200605083348.13880-1-benjamin.gaignard@st.com>
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#
+
+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-06-05 8:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 8:33 [PATCH v4 0/5] STM32 ETZPC bus controller Benjamin Gaignard
2020-06-05 8:33 ` [PATCH v4 1/5] dt-bindings: bus: Add firewall bindings Benjamin Gaignard
2020-06-05 8:33 ` [PATCH v4 2/5] bus: stm32: Introduce firewall controller helpers Benjamin Gaignard
2020-06-05 8:33 ` Benjamin Gaignard [this message]
2020-06-05 8:33 ` [PATCH v4 4/5] bus: stm32: Add stm32 ETZPC firewall bus controller Benjamin Gaignard
2020-06-05 8:33 ` [PATCH v4 5/5] ARM: dts: stm32: Use ETZPC firewall bus Benjamin Gaignard
2020-07-01 13:25 [PATCH v4 0/5] STM32 ETZPC bus controller 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
2020-07-20 9:21 ` 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=20200605083348.13880-4-benjamin.gaignard@st.com \
--to=benjamin.gaignard@st.com \
--cc=alexandre.torgue@st.com \
--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=robh+dt@kernel.org \
--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).