From: Lubomir Rintel <lkundrak@v3.sk>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Lubomir Rintel <lkundrak@v3.sk>
Subject: [PATCH 03/10] dt-bindings: clock: Convert marvell,mmp2-clock to json-schema
Date: Wed, 19 Feb 2020 08:33:46 +0100 [thread overview]
Message-ID: <20200219073353.184336-4-lkundrak@v3.sk> (raw)
In-Reply-To: <20200219073353.184336-1-lkundrak@v3.sk>
Convert the fixed-factor-clock binding to DT schema format using
json-schema.
While at that, fix a couple of small errors: make the file base name
match the compatible string, add an example and document the reg-names
property.
Signed-off-by: Lubomir Rintel <lkundrak@v3.sk>
---
.../bindings/clock/marvell,mmp2-clock.yaml | 62 +++++++++++++++++++
.../bindings/clock/marvell,mmp2.txt | 21 -------
2 files changed, 62 insertions(+), 21 deletions(-)
create mode 100644 Documentation/devicetree/bindings/clock/marvell,mmp2-clock.yaml
delete mode 100644 Documentation/devicetree/bindings/clock/marvell,mmp2.txt
diff --git a/Documentation/devicetree/bindings/clock/marvell,mmp2-clock.yaml b/Documentation/devicetree/bindings/clock/marvell,mmp2-clock.yaml
new file mode 100644
index 0000000000000..c5fc2ad0236dd
--- /dev/null
+++ b/Documentation/devicetree/bindings/clock/marvell,mmp2-clock.yaml
@@ -0,0 +1,62 @@
+# SPDX-License-Identifier: GPL-2.0
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/clock/marvell,mmp2-clock.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Marvell MMP2 Clock Controller
+
+maintainers:
+ - Lubomir Rintel <lkundrak@v3.sk>
+
+description: |
+ The MMP2 clock subsystem generates and supplies clock to various
+ controllers within the MMP2 SoC.
+
+ Each clock is assigned an identifier and client nodes use this identifier
+ to specify the clock which they consume.
+
+ All these identifiers could be found in <dt-bindings/clock/marvell,mmp2.h>.
+
+properties:
+ compatible:
+ const: marvell,mmp2-clock # controller compatible with MMP2 SoC
+
+ reg:
+ items:
+ - description: MPMU register region
+ - description: APMU register region
+ - description: APBC register region
+
+ reg-names:
+ items:
+ - const: mpmu
+ - const: apmu
+ - const: apbc
+
+ '#clock-cells':
+ const: 1
+
+ '#reset-cells':
+ const: 1
+
+required:
+ - compatible
+ - reg
+ - reg-names
+ - '#clock-cells'
+ - '#reset-cells'
+
+additionalProperties: false
+
+examples:
+ - |
+ clock-controller@d4050000 {
+ compatible = "marvell,mmp2-clock";
+ reg = <0xd4050000 0x1000>,
+ <0xd4282800 0x400>,
+ <0xd4015000 0x1000>;
+ reg-names = "mpmu", "apmu", "apbc";
+ #clock-cells = <1>;
+ #reset-cells = <1>;
+ };
diff --git a/Documentation/devicetree/bindings/clock/marvell,mmp2.txt b/Documentation/devicetree/bindings/clock/marvell,mmp2.txt
deleted file mode 100644
index 23b52dc02266a..0000000000000
--- a/Documentation/devicetree/bindings/clock/marvell,mmp2.txt
+++ /dev/null
@@ -1,21 +0,0 @@
-* Marvell MMP2 Clock Controller
-
-The MMP2 clock subsystem generates and supplies clock to various
-controllers within the MMP2 SoC.
-
-Required Properties:
-
-- compatible: should be one of the following.
- - "marvell,mmp2-clock" - controller compatible with MMP2 SoC.
-
-- reg: physical base address of the clock subsystem and length of memory mapped
- region. There are 3 places in SOC has clock control logic:
- "mpmu", "apmu", "apbc". So three reg spaces need to be defined.
-
-- #clock-cells: should be 1.
-- #reset-cells: should be 1.
-
-Each clock is assigned an identifier and client nodes use this identifier
-to specify the clock which they consume.
-
-All these identifiers could be found in <dt-bindings/clock/marvell,mmp2.h>.
--
2.24.1
next prev parent reply other threads:[~2020-02-19 7:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 7:33 [PATCH 00/10] MMP2 CLK Update Lubomir Rintel
2020-02-19 7:33 ` [PATCH 01/10] clk: mmp2: Remove a unused prototype Lubomir Rintel
2020-02-19 7:33 ` [PATCH 02/10] clk: mmp2: Constify some strings Lubomir Rintel
2020-02-19 7:33 ` Lubomir Rintel [this message]
2020-02-26 15:28 ` [PATCH 03/10] dt-bindings: clock: Convert marvell,mmp2-clock to json-schema Rob Herring
2020-02-19 7:33 ` [PATCH 04/10] clk: mmp2: Add support for PLL clock sources Lubomir Rintel
2020-02-19 7:33 ` [PATCH 05/10] clk: mmp2: Stop pretending PLL outputs are constant Lubomir Rintel
2020-02-19 7:33 ` [PATCH 06/10] dt-bindings: clock: Add MMP3 compatible string Lubomir Rintel
2020-02-26 15:28 ` Rob Herring
2020-02-19 7:33 ` [PATCH 07/10] clk: mmp2: Check for MMP3 Lubomir Rintel
2020-02-19 7:33 ` [PATCH 08/10] dt-bindings: marvell,mmp2: Add clock ids for MMP3 PLLs Lubomir Rintel
2020-02-26 15:29 ` Rob Herring
2020-02-19 7:33 ` [PATCH 09/10] clk: mmp2: Add PLLs that are available on MMP3 Lubomir Rintel
2020-02-19 7:33 ` [PATCH 10/10] ARM: dts: mmp3: Use the MMP3 compatible string for /clocks Lubomir Rintel
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=20200219073353.184336-4-lkundrak@v3.sk \
--to=lkundrak@v3.sk \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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).