From: Benjamin Gaignard <benjamin.gaignard@st.com>
To: <broonie@kernel.org>, <robh@kernel.org>, <arnd@arndb.de>,
<shawnguo@kernel.org>, <s.hauer@pengutronix.de>,
<fabio.estevam@nxp.com>, <sudeep.holla@arm.com>, <lkml@metux.net>
Cc: devicetree@vger.kernel.org,
Benjamin Gaignard <benjamin.gaignard@st.com>,
loic.pallardy@st.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-imx@nxp.com,
kernel@pengutronix.de, stefano.stabellini@xilinx.com,
system-dt@lists.openampproject.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/7] dt-bindings: bus: Add firewall bindings
Date: Tue, 28 Jan 2020 16:38:00 +0100 [thread overview]
Message-ID: <20200128153806.7780-2-benjamin.gaignard@st.com> (raw)
In-Reply-To: <20200128153806.7780-1-benjamin.gaignard@st.com>
Add schemas for firewall consumer and provider.
Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
---
version 2:
- describe bindings in yaml files
.../bindings/bus/firewall/firewall-consumer.yaml | 25 ++++++++++++++++++++++
.../bindings/bus/firewall/firewall-provider.yaml | 18 ++++++++++++++++
2 files changed, 43 insertions(+)
create mode 100644 Documentation/devicetree/bindings/bus/firewall/firewall-consumer.yaml
create mode 100644 Documentation/devicetree/bindings/bus/firewall/firewall-provider.yaml
diff --git a/Documentation/devicetree/bindings/bus/firewall/firewall-consumer.yaml b/Documentation/devicetree/bindings/bus/firewall/firewall-consumer.yaml
new file mode 100644
index 000000000000..ea7963c600f7
--- /dev/null
+++ b/Documentation/devicetree/bindings/bus/firewall/firewall-consumer.yaml
@@ -0,0 +1,25 @@
+# SPDX-License-Identifier: BSD-2-Clause
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/bus/firewall/firewall-consumer.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Common Bus Firewall consumer binding
+
+maintainers:
+ - Benjamin Gaignard <benjamin.gaignard@st.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/firewall/firewall-provider.yaml b/Documentation/devicetree/bindings/bus/firewall/firewall-provider.yaml
new file mode 100644
index 000000000000..0f9a38b63fbe
--- /dev/null
+++ b/Documentation/devicetree/bindings/bus/firewall/firewall-provider.yaml
@@ -0,0 +1,18 @@
+# SPDX-License-Identifier: BSD-2-Clause
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/bus/firewall/firewall-provider.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Common Bus Firewall provider binding
+
+maintainers:
+ - Benjamin Gaignard <benjamin.gaignard@st.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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-01-28 15:39 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 15:37 [PATCH v2 0/7] Introduce bus firewall controller framework Benjamin Gaignard
2020-01-28 15:38 ` Benjamin Gaignard [this message]
2020-01-28 15:38 ` [PATCH v2 2/7] bus: Introduce " Benjamin Gaignard
2020-01-28 15:52 ` Greg KH
2020-01-28 16:41 ` Benjamin GAIGNARD
2020-01-28 16:57 ` Greg KH
2020-01-28 20:29 ` Benjamin GAIGNARD
2020-01-29 5:49 ` Greg KH
2020-01-29 9:42 ` Linus Walleij
2020-01-29 9:52 ` Greg KH
2020-01-29 11:17 ` Mark Brown
2020-01-31 8:37 ` Benjamin GAIGNARD
2020-01-31 9:06 ` Greg KH
2020-02-14 16:05 ` Linus Walleij
2020-02-14 21:40 ` Greg KH
2020-02-15 12:41 ` Benjamin GAIGNARD
2020-02-16 7:21 ` Greg KH
2020-01-28 15:38 ` [PATCH v2 3/7] base: Add calls to firewall controller Benjamin Gaignard
2020-01-28 15:38 ` [PATCH v2 4/7] dt-bindings: bus: Add STM32 ETZPC " Benjamin Gaignard
2020-01-28 15:38 ` [PATCH v2 5/7] bus: firewall: Add driver for STM32 ETZPC controller Benjamin Gaignard
2020-01-28 15:38 ` [PATCH v2 6/7] ARM: dts: stm32: Add firewall node for stm32mp157 SoC Benjamin Gaignard
2020-01-28 15:38 ` [PATCH v2 7/7] ARM: dts: stm32: enable firewall controller node on stm32mp157c-ed1 Benjamin Gaignard
2020-01-28 16:36 ` [PATCH v2 0/7] Introduce bus firewall controller framework Sudeep Holla
2020-01-28 16:46 ` Benjamin GAIGNARD
2020-01-28 17:17 ` Sudeep Holla
2020-01-28 20:06 ` Benjamin GAIGNARD
2020-01-28 22:06 ` Robin Murphy
2020-01-29 13:40 ` Benjamin GAIGNARD
2020-01-31 18:25 ` Robin Murphy
2020-02-03 13:16 ` Benjamin GAIGNARD
2020-01-31 20:51 ` Florian Fainelli
2020-02-03 13:41 ` Benjamin GAIGNARD
2020-01-31 20:48 ` Florian Fainelli
2020-02-02 12:23 ` 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=20200128153806.7780-2-benjamin.gaignard@st.com \
--to=benjamin.gaignard@st.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=devicetree@vger.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=lkml@metux.net \
--cc=loic.pallardy@st.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefano.stabellini@xilinx.com \
--cc=sudeep.holla@arm.com \
--cc=system-dt@lists.openampproject.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).