From: Philipp Zabel <p.zabel@pengutronix.de>
To: devicetree@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Neil Armstrong <narmstrong@baylibre.com>,
linux-kernel@vger.kernel.org, Antoine Tenart <atenart@kernel.org>
Subject: [PATCH 03/14] dt-bindings: reset: berlin: Convert to yaml
Date: Thu, 7 Apr 2022 17:43:27 +0200 [thread overview]
Message-ID: <20220407154338.4190674-3-p.zabel@pengutronix.de> (raw)
In-Reply-To: <20220407154338.4190674-1-p.zabel@pengutronix.de>
Convert the device tree bindings for the Marvell Berlin reset controller
to YAML schema to allow participating in DT validation.
Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
Cc: Antoine Tenart <atenart@kernel.org>
---
.../bindings/reset/berlin,reset.txt | 23 -----------
.../bindings/reset/marvell,berlin2-reset.yaml | 38 +++++++++++++++++++
2 files changed, 38 insertions(+), 23 deletions(-)
delete mode 100644 Documentation/devicetree/bindings/reset/berlin,reset.txt
create mode 100644 Documentation/devicetree/bindings/reset/marvell,berlin2-reset.yaml
diff --git a/Documentation/devicetree/bindings/reset/berlin,reset.txt b/Documentation/devicetree/bindings/reset/berlin,reset.txt
deleted file mode 100644
index 514fee098b4b..000000000000
--- a/Documentation/devicetree/bindings/reset/berlin,reset.txt
+++ /dev/null
@@ -1,23 +0,0 @@
-Marvell Berlin reset controller
-===============================
-
-Please also refer to reset.txt in this directory for common reset
-controller binding usage.
-
-The reset controller node must be a sub-node of the chip controller
-node on Berlin SoCs.
-
-Required properties:
-- compatible: should be "marvell,berlin2-reset"
-- #reset-cells: must be set to 2
-
-Example:
-
-chip_rst: reset {
- compatible = "marvell,berlin2-reset";
- #reset-cells = <2>;
-};
-
-&usb_phy0 {
- resets = <&chip_rst 0x104 12>;
-};
diff --git a/Documentation/devicetree/bindings/reset/marvell,berlin2-reset.yaml b/Documentation/devicetree/bindings/reset/marvell,berlin2-reset.yaml
new file mode 100644
index 000000000000..d71d0f0a13ee
--- /dev/null
+++ b/Documentation/devicetree/bindings/reset/marvell,berlin2-reset.yaml
@@ -0,0 +1,38 @@
+# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
+# Copyright 2015 Antoine Tenart <atenart@kernel.org>
+%YAML 1.2
+---
+$id: "http://devicetree.org/schemas/reset/marvell,berlin2-reset.yaml#"
+$schema: "http://devicetree.org/meta-schemas/core.yaml#"
+
+title: Marvell Berlin reset controller
+
+maintainers:
+ - Antoine Tenart <atenart@kernel.org>
+
+description: The reset controller node must be a sub-node of the chip
+ controller node on Berlin SoCs.
+
+properties:
+ compatible:
+ const: marvell,berlin2-reset
+
+ "#reset-cells":
+ const: 2
+
+required:
+ - compatible
+ - "#reset-cells"
+
+additionalProperties: false
+
+examples:
+ - |
+ chip: chip-control@ea0000 {
+ reg = <0xea0000 0x400>;
+
+ chip_rst: reset {
+ compatible = "marvell,berlin2-reset";
+ #reset-cells = <2>;
+ };
+ };
--
2.30.2
next prev parent reply other threads:[~2022-04-07 15:44 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 15:43 [PATCH 01/14] dt-bindings: reset: amlogic,meson-axg-audio-arb: Convert to yaml Philipp Zabel
2022-04-07 15:43 ` [PATCH 02/14] dt-bindings: reset: ath79: " Philipp Zabel
2022-04-08 21:03 ` Rob Herring
2022-04-07 15:43 ` Philipp Zabel [this message]
2022-04-08 21:04 ` [PATCH 03/14] dt-bindings: reset: berlin: " Rob Herring
2022-04-07 15:43 ` [PATCH 04/14] dt-bindings: reset: bitmain,bm1880-reset: " Philipp Zabel
2022-04-08 21:05 ` Rob Herring
2022-04-07 15:43 ` [PATCH 05/14] dt-bindings: reset: lantiq,reset: " Philipp Zabel
2022-04-08 21:07 ` Rob Herring
2022-04-18 16:34 ` Martin Blumenstingl
2022-05-02 15:39 ` Philipp Zabel
2022-04-07 15:43 ` [PATCH 06/14] dt-bindings: reset: nuvoton,npcm-reset: " Philipp Zabel
2022-04-08 21:08 ` Rob Herring
2022-04-07 15:43 ` [PATCH 07/14] dt-bindings: reset: oxsemi,oxnas-reset: " Philipp Zabel
2022-04-08 15:43 ` Rob Herring
2022-04-07 15:43 ` [PATCH 08/14] dt-bindings: reset: snps,axs10x-reset: " Philipp Zabel
2022-04-08 21:09 ` Rob Herring
2022-04-07 15:43 ` [PATCH 09/14] dt-bindings: reset: snps,dw-reset: " Philipp Zabel
2022-04-08 15:43 ` Rob Herring
2022-04-08 18:25 ` Rob Herring
2022-04-11 13:59 ` Philipp Zabel
2025-01-07 15:22 ` Rob Herring
2022-04-07 15:43 ` [PATCH 10/14] dt-bindings: reset: snps,hsdk-reset: " Philipp Zabel
2022-04-08 21:12 ` Rob Herring
2022-04-07 15:43 ` [PATCH 11/14] dt-bindings: reset: socfpga: " Philipp Zabel
2022-04-08 21:12 ` Rob Herring
2022-04-07 15:43 ` [PATCH 12/14] dt-bindings: reset: st,sti-picophyreset: " Philipp Zabel
2022-04-08 21:13 ` Rob Herring
2022-04-07 15:43 ` [PATCH 13/14] dt-bindings: reset: st,sti-powerdown: " Philipp Zabel
2022-04-08 21:14 ` Rob Herring
2022-04-07 15:43 ` [PATCH 14/14] dt-bindings: reset: " Philipp Zabel
2022-04-07 20:04 ` Rob Herring
2022-05-05 1:08 ` Stephen Warren
2022-08-25 15:53 ` Rob Herring
2022-08-25 16:17 ` Stephen Warren
2022-04-08 21:03 ` [PATCH 01/14] dt-bindings: reset: amlogic,meson-axg-audio-arb: " Rob Herring
2022-04-18 16:32 ` Martin Blumenstingl
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=20220407154338.4190674-3-p.zabel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=atenart@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=narmstrong@baylibre.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).