From: Rob Herring <robh@kernel.org>
To: Fabien Parent <fparent@baylibre.com>
Cc: Matt Mackall <mpm@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Matthias Brugger <matthias.bgg@gmail.com>,
Sean Wang <sean.wang@mediatek.com>,
mkorpershoek@baylibre.com, linux-crypto@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: rng: mediatek: convert to yaml schema
Date: Wed, 19 May 2021 17:04:21 -0500 [thread overview]
Message-ID: <20210519220421.GA3738290@robh.at.kernel.org> (raw)
In-Reply-To: <20210518112250.2146819-1-fparent@baylibre.com>
On Tue, May 18, 2021 at 01:22:49PM +0200, Fabien Parent wrote:
> Convert the RNG binding for MediaTek to use YAML schema.
>
> Signed-off-by: Fabien Parent <fparent@baylibre.com>
> ---
> .../devicetree/bindings/rng/mtk-rng.txt | 22 --------
> .../devicetree/bindings/rng/mtk-rng.yaml | 53 +++++++++++++++++++
> 2 files changed, 53 insertions(+), 22 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/rng/mtk-rng.txt
> create mode 100644 Documentation/devicetree/bindings/rng/mtk-rng.yaml
>
> diff --git a/Documentation/devicetree/bindings/rng/mtk-rng.txt b/Documentation/devicetree/bindings/rng/mtk-rng.txt
> deleted file mode 100644
> index dfdcb5cd2ea8..000000000000
> --- a/Documentation/devicetree/bindings/rng/mtk-rng.txt
> +++ /dev/null
> @@ -1,22 +0,0 @@
> -Device-Tree bindings for Mediatek random number generator
> -found in MediaTek SoC family
> -
> -Required properties:
> -- compatible : Should be
> - "mediatek,mt7622-rng", "mediatek,mt7623-rng" : for MT7622
> - "mediatek,mt7629-rng", "mediatek,mt7623-rng" : for MT7629
> - "mediatek,mt7623-rng" : for MT7623
> - "mediatek,mt8516-rng", "mediatek,mt7623-rng" : for MT8516
> -- clocks : list of clock specifiers, corresponding to
> - entries in clock-names property;
> -- clock-names : Should contain "rng" entries;
> -- reg : Specifies base physical address and size of the registers
> -
> -Example:
> -
> -rng: rng@1020f000 {
> - compatible = "mediatek,mt7623-rng";
> - reg = <0 0x1020f000 0 0x1000>;
> - clocks = <&infracfg CLK_INFRA_TRNG>;
> - clock-names = "rng";
> -};
> diff --git a/Documentation/devicetree/bindings/rng/mtk-rng.yaml b/Documentation/devicetree/bindings/rng/mtk-rng.yaml
> new file mode 100644
> index 000000000000..d9731f0ae47d
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/rng/mtk-rng.yaml
> @@ -0,0 +1,53 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/rng/mtk-rng.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: MediaTek Random number generator
> +
> +maintainers:
> + - Sean Wang <sean.wang@mediatek.com>
> +
> +properties:
> + compatible:
> + oneOf:
> + - enum:
> + - mediatek,mt7623-rng
> + - items:
> + - const: mediatek,mt7622-rng
> + - const: mediatek,mt7623-rng
> + - items:
> + - const: mediatek,mt7629-rng
> + - const: mediatek,mt7623-rng
> + - items:
> + - const: mediatek,mt8516-rng
> + - const: mediatek,mt7623-rng
The last 3 can be:
- items:
- enum:
- mediatek,mt7622-rng
- mediatek,mt7629-rng
- mediatek,mt8516-rng
- const: mediatek,mt7623-rng
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + clock-names:
> + items:
> + - const: rng
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - clock-names
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/clock/mt2701-clk.h>
> + rng: rng@1020f000 {
> + compatible = "mediatek,mt7623-rng";
> + reg = <0x1020f000 0x1000>;
> + clocks = <&infracfg CLK_INFRA_TRNG>;
> + clock-names = "rng";
> + };
> --
> 2.31.1
>
prev parent reply other threads:[~2021-05-19 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 11:22 [PATCH 1/2] dt-bindings: rng: mediatek: convert to yaml schema Fabien Parent
2021-05-18 11:22 ` [PATCH 2/2] dt-bindings: rng: mediatek: add mt8365 to mtk rng binding Fabien Parent
2021-05-19 22:04 ` Rob Herring [this message]
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=20210519220421.GA3738290@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fparent@baylibre.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mkorpershoek@baylibre.com \
--cc=mpm@selenic.com \
--cc=sean.wang@mediatek.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;
as well as URLs for NNTP newsgroup(s).