From: Gatien Chevallier <gatien.chevallier@foss.st.com>
To: <alexandre.torgue@foss.st.com>, <robh+dt@kernel.org>,
<Oleksii_Moisieiev@epam.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>, <loic.pallardy@st.com>,
<devicetree@vger.kernel.org>, <mark.rutland@arm.com>,
<arnd@arndb.de>, <gatien.chevallier@foss.st.com>
Subject: [RFC PATCH v2 2/7] dt-bindings: bus: add STM32 System Bus
Date: Thu, 22 Dec 2022 11:04:59 +0100 [thread overview]
Message-ID: <20221222100504.68247-3-gatien.chevallier@foss.st.com> (raw)
In-Reply-To: <20221222100504.68247-1-gatien.chevallier@foss.st.com>
Document STM32 System Bus. This bus is intended to control firewall
access for the peripherals connected to it.
Signed-off-by: Gatien Chevallier <gatien.chevallier@foss.st.com>
Signed-off-by: Loic PALLARDY <loic.pallardy@st.com>
---
Changes in V2:
- Corrected errors highlighted by Rob's robot
- Re-ordered Signed-off-by tags
.../devicetree/bindings/bus/st,sys-bus.yaml | 88 +++++++++++++++++++
1 file changed, 88 insertions(+)
create mode 100644 Documentation/devicetree/bindings/bus/st,sys-bus.yaml
diff --git a/Documentation/devicetree/bindings/bus/st,sys-bus.yaml b/Documentation/devicetree/bindings/bus/st,sys-bus.yaml
new file mode 100644
index 000000000000..d246fbdd6dea
--- /dev/null
+++ b/Documentation/devicetree/bindings/bus/st,sys-bus.yaml
@@ -0,0 +1,88 @@
+# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/bus/st,sys-bus.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: STM32 System Bus
+
+description: |
+ The STM32 System Bus is an internal bus to which some internal peripherals
+ are connected. STM32 System Bus integrates a firewall controlling access to each
+ device. This bus prevents non-accessible devices to be probed.
+
+ To see which peripherals are securable, please check the SoC reference manual.
+
+maintainers:
+ - Gatien Chevallier <gatien.chevallier@foss.st.com>
+
+allOf:
+ - $ref: /schemas/feature-controllers/feature-domain-controller.yaml#
+
+properties:
+ compatible:
+ enum:
+ - st,stm32mp13-sys-bus
+ - st,stm32mp15-sys-bus
+
+ reg:
+ maxItems: 1
+
+ "#address-cells":
+ const: 1
+
+ "#size-cells":
+ const: 1
+
+ '#feature-domain-cells':
+ minimum: 1
+
+ ranges: true
+
+ feature-domain-controller: true
+
+patternProperties:
+ "^.*@[0-9a-f]+$":
+ description: Devices attached to system bus
+ type: object
+ properties:
+ feature-domains:
+ $ref: /schemas/feature-controllers/feature-domain-controller.yaml#/properties/feature-domains
+
+required:
+ - compatible
+ - reg
+ - "#address-cells"
+ - "#size-cells"
+ - feature-domain-controller
+ - '#feature-domain-cells'
+ - ranges
+
+additionalProperties: false
+
+examples:
+ - |
+ // In this example,
+ // - the foo1 device refers to etzpc as his domain controller.
+ // - same goes for foo2.
+ // Access rights are verified before creating devices.
+
+ etzpc: etzpc@5c007000 {
+ compatible = "st,stm32mp15-sys-bus";
+ reg = <0x5c007000 0x400>;
+ #address-cells = <1>;
+ #size-cells = <1>;
+ ranges;
+ feature-domain-controller;
+ #feature-domain-cells = <1>;
+
+ foo1: foo@1000000 {
+ reg = <0x0 0x1000000>;
+ feature-domains = <&etzpc 0>;
+ };
+
+ foo2: foo@2000000 {
+ reg = <0x0 0x2000000>;
+ feature-domains = <&etzpc 0>;
+ };
+ };
--
2.25.1
next prev parent reply other threads:[~2022-12-22 10:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 10:04 [RFC PATCH v2 0/7] Introduce STM32 system bus Gatien Chevallier
2022-12-22 10:04 ` [RFC PATCH v2 1/7] dt-bindings: Document common device controller bindings Gatien Chevallier
2022-12-23 10:08 ` Krzysztof Kozlowski
2022-12-22 10:04 ` Gatien Chevallier [this message]
2022-12-22 10:05 ` [RFC PATCH v2 3/7] dt-bindings: bus: add STM32MP15 ETZPC firewall bus bindings Gatien Chevallier
2022-12-22 10:05 ` [RFC PATCH v2 4/7] dt-bindings: bus: add STM32MP13 " Gatien Chevallier
2022-12-22 16:39 ` [RFC PATCH v2 0/7] Introduce STM32 system bus Greg KH
2023-01-03 9:45 ` Gatien CHEVALLIER
2023-01-04 6:10 ` Greg KH
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=20221222100504.68247-3-gatien.chevallier@foss.st.com \
--to=gatien.chevallier@foss.st.com \
--cc=Oleksii_Moisieiev@epam.com \
--cc=alexandre.torgue@foss.st.com \
--cc=arnd@arndb.de \
--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=loic.pallardy@st.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).