From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: "Nícolas F. R. A. Prado" <nfraprado@protonmail.com>,
devicetree@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Scott Branden <sbranden@broadcom.com>,
linux-arm-kernel@lists.infradead.org, Ray Jui <rjui@broadcom.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
bcm-kernel-feedback-list@broadcom.com,
linux-crypto@vger.kernel.org, Matt Mackall <mpm@selenic.com>,
linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH] dt-bindings: rng: Convert BCM2835 to DT schema
Date: Mon, 10 Feb 2020 13:09:54 +0100 [thread overview]
Message-ID: <2bd9936d106948210b7a34c8060600572318600c.camel@suse.de> (raw)
In-Reply-To: <20200207231347.2908737-1-nfraprado@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 4289 bytes --]
On Fri, 2020-02-07 at 23:14 +0000, Nícolas F. R. A. Prado wrote:
> Convert BCM2835/6368 Random number generator bindings to DT schema.
>
> Signed-off-by: Nícolas F. R. A. Prado <nfraprado@protonmail.com>
> ---
Reviewed-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Thanks!
> Hi,
> wasn't really clear to me who to add as maintainer for this dt-binding.
> The three names added here as maintainers were based on the get_maintainer
> script and on previous commits on this file.
> Please tell me whether these are the right maintainers for this file or not.
Looks OK to me. When in doubt I just trust get_maintainer, never failed me so
far.
> This patch was tested with:
> make ARCH=arm
> DT_SCHEMA_FILES=Documentation/devicetree/bindings/rng/brcm,bcm2835.yaml
> dt_binding_check
> make ARCH=arm
> DT_SCHEMA_FILES=Documentation/devicetree/bindings/rng/brcm,bcm2835.yaml
> dtbs_check
>
> Thanks,
> Nícolas
>
> .../devicetree/bindings/rng/brcm,bcm2835.txt | 40 ------------
> .../devicetree/bindings/rng/brcm,bcm2835.yaml | 61 +++++++++++++++++++
> 2 files changed, 61 insertions(+), 40 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/rng/brcm,bcm2835.txt
> create mode 100644 Documentation/devicetree/bindings/rng/brcm,bcm2835.yaml
>
> diff --git a/Documentation/devicetree/bindings/rng/brcm,bcm2835.txt
> b/Documentation/devicetree/bindings/rng/brcm,bcm2835.txt
> deleted file mode 100644
> index aaac7975f61c..000000000000
> --- a/Documentation/devicetree/bindings/rng/brcm,bcm2835.txt
> +++ /dev/null
> @@ -1,40 +0,0 @@
> -BCM2835/6368 Random number generator
> -
> -Required properties:
> -
> -- compatible : should be one of
> - "brcm,bcm2835-rng"
> - "brcm,bcm-nsp-rng"
> - "brcm,bcm5301x-rng" or
> - "brcm,bcm6368-rng"
> -- reg : Specifies base physical address and size of the registers.
> -
> -Optional properties:
> -
> -- clocks : phandle to clock-controller plus clock-specifier pair
> -- clock-names : "ipsec" as a clock name
> -
> -Optional properties:
> -
> -- interrupts: specify the interrupt for the RNG block
> -
> -Example:
> -
> -rng {
> - compatible = "brcm,bcm2835-rng";
> - reg = <0x7e104000 0x10>;
> - interrupts = <2 29>;
> -};
> -
> -rng@18033000 {
> - compatible = "brcm,bcm-nsp-rng";
> - reg = <0x18033000 0x14>;
> -};
> -
> -random: rng@10004180 {
> - compatible = "brcm,bcm6368-rng";
> - reg = <0x10004180 0x14>;
> -
> - clocks = <&periph_clk 18>;
> - clock-names = "ipsec";
> -};
> diff --git a/Documentation/devicetree/bindings/rng/brcm,bcm2835.yaml
> b/Documentation/devicetree/bindings/rng/brcm,bcm2835.yaml
> new file mode 100644
> index 000000000000..b1621031721e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/rng/brcm,bcm2835.yaml
> @@ -0,0 +1,61 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/rng/brcm,bcm2835.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: BCM2835/6368 Random number generator
> +
> +maintainers:
> + - Stefan Wahren <stefan.wahren@i2se.com>
> + - Florian Fainelli <f.fainelli@gmail.com>
> + - Herbert Xu <herbert@gondor.apana.org.au>
> +
> +properties:
> + compatible:
> + enum:
> + - brcm,bcm2835-rng
> + - brcm,bcm-nsp-rng
> + - brcm,bcm5301x-rng
> + - brcm,bcm6368-rng
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + description: phandle to clock-controller plus clock-specifier pair
> + maxItems: 1
> +
> + clock-names:
> + const: ipsec
> +
> + interrupts:
> + description: specify the interrupt for the RNG block
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> +
> +examples:
> + - |
> + rng {
> + compatible = "brcm,bcm2835-rng";
> + reg = <0x7e104000 0x10>;
> + interrupts = <2 29>;
> + };
> +
> + - |
> + rng@18033000 {
> + compatible = "brcm,bcm-nsp-rng";
> + reg = <0x18033000 0x14>;
> + };
> +
> + - |
> + random: rng@10004180 {
> + compatible = "brcm,bcm6368-rng";
> + reg = <0x10004180 0x14>;
> +
> + clocks = <&periph_clk 18>;
> + clock-names = "ipsec";
> + };
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-02-10 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 23:14 [PATCH] dt-bindings: rng: Convert BCM2835 to DT schema Nícolas F. R. A. Prado
2020-02-09 3:36 ` Florian Fainelli
2020-02-09 3:36 ` Florian Fainelli
2020-02-10 12:09 ` Nicolas Saenz Julienne [this message]
2020-02-19 22:06 ` Rob Herring
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=2bd9936d106948210b7a34c8060600572318600c.camel@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.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-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mpm@selenic.com \
--cc=nfraprado@protonmail.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.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).