From: Rob Herring <robh@kernel.org>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: "Russell King" <linux@armlinux.org.uk>,
"Daniel Lezcano" <daniel.lezcano@linaro.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH 1/3] dt-bindings: arm: mediatek: convert hifsys to the json-schema
Date: Tue, 30 Jan 2024 14:36:17 -0600 [thread overview]
Message-ID: <20240130203617.GB2290196-robh@kernel.org> (raw)
In-Reply-To: <20240123082100.7334-2-zajec5@gmail.com>
On Tue, Jan 23, 2024 at 09:20:58AM +0100, Rafał Miłecki wrote:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> This helps validating DTS files. Introduced changes:
> 1. Documented "reg" property
> 2. Documented "#reset-cells" property
> 3. Adjusted "reg" in example
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
> ---
> .../bindings/arm/mediatek/mediatek,hifsys.txt | 26 ---------
> .../arm/mediatek/mediatek,mt2701-hifsys.yaml | 54 +++++++++++++++++++
Like the other one, please move this.
> 2 files changed, 54 insertions(+), 26 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,hifsys.txt
> create mode 100644 Documentation/devicetree/bindings/arm/mediatek/mediatek,mt2701-hifsys.yaml
>
> diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,hifsys.txt b/Documentation/devicetree/bindings/arm/mediatek/mediatek,hifsys.txt
> deleted file mode 100644
> index 323905af82c3..000000000000
> --- a/Documentation/devicetree/bindings/arm/mediatek/mediatek,hifsys.txt
> +++ /dev/null
> @@ -1,26 +0,0 @@
> -Mediatek hifsys controller
> -============================
> -
> -The Mediatek hifsys controller provides various clocks and reset
> -outputs to the system.
> -
> -Required Properties:
> -
> -- compatible: Should be:
> - - "mediatek,mt2701-hifsys", "syscon"
> - - "mediatek,mt7622-hifsys", "syscon"
> - - "mediatek,mt7623-hifsys", "mediatek,mt2701-hifsys", "syscon"
> -- #clock-cells: Must be 1
> -
> -The hifsys controller uses the common clk binding from
> -Documentation/devicetree/bindings/clock/clock-bindings.txt
> -The available clocks are defined in dt-bindings/clock/mt*-clk.h.
> -
> -Example:
> -
> -hifsys: clock-controller@1a000000 {
> - compatible = "mediatek,mt2701-hifsys", "syscon";
> - reg = <0 0x1a000000 0 0x1000>;
> - #clock-cells = <1>;
> - #reset-cells = <1>;
> -};
> diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt2701-hifsys.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt2701-hifsys.yaml
> new file mode 100644
> index 000000000000..7c7b7b7b1142
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mt2701-hifsys.yaml
> @@ -0,0 +1,54 @@
> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/arm/mediatek/mediatek,mt2701-hifsys.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Mediatek hifsys controller
> +
> +description:
> + The Mediatek hifsys controller provides various clocks and reset outputs to
> + the system.
> +
> +maintainers:
> + - Matthias Brugger <matthias.bgg@gmail.com>
> +
> +properties:
> + compatible:
> + oneOf:
> + - items:
> + - const: mediatek,mt2701-hifsys
> + - const: syscon
> + - items:
> + - enum:
> + - mediatek,mt7623-hifsys
> + - const: mediatek,mt2701-hifsys
> + - const: syscon
> + - items:
> + - const: mediatek,mt7622-hifsys
> + - const: syscon
The 1st and 3rd entries can be combined.
> +
> + reg:
> + maxItems: 1
> +
> + "#clock-cells":
> + const: 1
> + description: The available clocks are defined in dt-bindings/clock/mt*-clk.h
> +
> + "#reset-cells":
> + const: 1
> +
> +required:
> + - reg
> + - "#clock-cells"
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + clock-controller@1a000000 {
> + compatible = "mediatek,mt2701-hifsys", "syscon";
> + reg = <0x1a000000 0x1000>;
> + #clock-cells = <1>;
> + #reset-cells = <1>;
> + };
> --
> 2.35.3
>
next prev parent reply other threads:[~2024-01-30 20:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 8:20 [PATCH 0/3] dt-bindings: arm: mediatek: convert MT7622-related bindings to the json-schema Rafał Miłecki
2024-01-23 8:20 ` [PATCH 1/3] dt-bindings: arm: mediatek: convert hifsys " Rafał Miłecki
2024-01-30 20:36 ` Rob Herring [this message]
2024-01-23 8:20 ` [PATCH 2/3] dt-bindings: arm: mediatek: convert PCIESYS " Rafał Miłecki
2024-01-23 11:20 ` AngeloGioacchino Del Regno
2024-01-30 20:34 ` Rob Herring
2024-01-30 21:57 ` Rafał Miłecki
2024-01-31 8:32 ` AngeloGioacchino Del Regno
2024-01-23 8:21 ` [PATCH 3/3] dt-bindings: arm: mediatek: convert SSUSBSYS " Rafał Miłecki
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=20240130203617.GB2290196-robh@kernel.org \
--to=robh@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=matthias.bgg@gmail.com \
--cc=rafal@milecki.pl \
--cc=tglx@linutronix.de \
--cc=zajec5@gmail.com \
/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