[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200701132523.32533-2-benjamin.gaignard@st.com>
Date: Wed, 1 Jul 2020 15:25:19 +0200
From: Benjamin Gaignard <benjamin.gaignard@...com>
To: <robh+dt@...nel.org>, <mcoquelin.stm32@...il.com>,
<alexandre.torgue@...com>, <linus.walleij@...aro.org>,
<gregkh@...uxfoundation.org>
CC: <linux-stm32@...md-mailman.stormreply.com>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <stefano.stabellini@...inx.com>,
<tomase@...inx.com>, <devicetree@...r.kernel.org>,
Benjamin Gaignard <benjamin.gaignard@...com>
Subject: [PATCH v4 1/5] dt-bindings: bus: Add firewall bindings
Add schemas for firewall consumer and provider.
Signed-off-by: Benjamin Gaignard <benjamin.gaignard@...com>
Reviewed-by: Linus Walleij <linus.walleij@...aro.org>
---
.../bindings/bus/stm32/firewall-consumer.yaml | 36 ++++++++++++++++++++++
.../bindings/bus/stm32/firewall-provider.yaml | 18 +++++++++++
2 files changed, 54 insertions(+)
create mode 100644 Documentation/devicetree/bindings/bus/stm32/firewall-consumer.yaml
create mode 100644 Documentation/devicetree/bindings/bus/stm32/firewall-provider.yaml
diff --git a/Documentation/devicetree/bindings/bus/stm32/firewall-consumer.yaml b/Documentation/devicetree/bindings/bus/stm32/firewall-consumer.yaml
new file mode 100644
index 000000000000..d3d76f99b38d
--- /dev/null
+++ b/Documentation/devicetree/bindings/bus/stm32/firewall-consumer.yaml
@@ -0,0 +1,36 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/bus/stm32/firewall-consumer.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Common Bus Firewall consumer binding
+
+description: |
+ Firewall properties provide the possible firewall bus controller
+ configurations for a device.
+ Bus firewall controllers are typically used to control if a hardware
+ block can perform read or write operations on bus.
+ The contents of the firewall bus configuration properties are defined by
+ the binding for the individual firewall controller device.
+
+ The first configuration 'firewall-0' or the one named 'default' is
+ applied before probing the device itself.
+
+maintainers:
+ - Benjamin Gaignard <benjamin.gaignard@...com>
+
+# always select the core schema
+select: true
+
+properties:
+ firewall-0: true
+
+ firewall-names: true
+
+patternProperties:
+ "firewall-[0-9]":
+ $ref: "/schemas/types.yaml#/definitions/phandle-array"
+
+dependencies:
+ firewall-names: [ firewall-0 ]
diff --git a/Documentation/devicetree/bindings/bus/stm32/firewall-provider.yaml b/Documentation/devicetree/bindings/bus/stm32/firewall-provider.yaml
new file mode 100644
index 000000000000..299824c620ea
--- /dev/null
+++ b/Documentation/devicetree/bindings/bus/stm32/firewall-provider.yaml
@@ -0,0 +1,18 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/bus/stm32/firewall-provider.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Common Bus Firewall provider binding
+
+maintainers:
+ - Benjamin Gaignard <benjamin.gaignard@...com>
+
+properties:
+ '#firewall-cells':
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description: Number of cells in a bus firewall specifier
+
+required:
+ - '#firewall-cells'
--
2.15.0
Powered by blists - more mailing lists