From: "Álvaro Fernández Rojas" <noltari@gmail.com>
To: "Matt Mackall" <mpm@selenic.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Rob Herring" <robh+dt@kernel.org>,
"Nicolas Saenz Julienne" <nsaenzjulienne@suse.de>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"Ray Jui" <rjui@broadcom.com>,
"Scott Branden" <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
"Philipp Zabel" <p.zabel@pengutronix.de>,
"Álvaro Fernández Rojas" <noltari@gmail.com>,
"Lee Jones" <lee.jones@linaro.org>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
"Alexandru Ardelean" <alexandru.ardelean@analog.com>,
"Rikard Falkeborn" <rikard.falkeborn@gmail.com>,
"Tian Tao" <tiantao6@hisilicon.com>,
"Stefan Wahren" <stefan.wahren@i2se.com>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v6 1/3] dt-bindings: rng: bcm2835: add clock constraints
Date: Fri, 5 Mar 2021 08:01:30 +0100 [thread overview]
Message-ID: <20210305070132.2986-2-noltari@gmail.com> (raw)
In-Reply-To: <20210305070132.2986-1-noltari@gmail.com>
brcm,bcm6368-rng controllers require enabling the IPSEC clock in order to get
a functional RNG.
Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
---
v6: add new patch making clocks mandatory for BCM6368.
.../devicetree/bindings/rng/brcm,bcm2835.yaml | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/Documentation/devicetree/bindings/rng/brcm,bcm2835.yaml b/Documentation/devicetree/bindings/rng/brcm,bcm2835.yaml
index c147900f9041..5174492e22f3 100644
--- a/Documentation/devicetree/bindings/rng/brcm,bcm2835.yaml
+++ b/Documentation/devicetree/bindings/rng/brcm,bcm2835.yaml
@@ -35,6 +35,16 @@ required:
- compatible
- reg
+if:
+ properties:
+ compatible:
+ enum:
+ - brcm,bcm6368-rng
+then:
+ required:
+ - clocks
+ - clock-names
+
additionalProperties: false
examples:
--
2.20.1
next prev parent reply other threads:[~2021-03-05 7:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 7:01 [PATCH v6 0/3] hwrng: bcm2835: add reset support Álvaro Fernández Rojas
2021-03-05 7:01 ` Álvaro Fernández Rojas [this message]
2021-03-08 21:52 ` [PATCH v6 1/3] dt-bindings: rng: bcm2835: add clock constraints Rob Herring
2021-03-08 22:02 ` Florian Fainelli
2021-03-05 7:01 ` [PATCH v6 2/3] dt-bindings: rng: bcm2835: document reset support Álvaro Fernández Rojas
2021-03-08 21:53 ` Rob Herring
2021-03-08 22:02 ` Florian Fainelli
2021-03-05 7:01 ` [PATCH v6 3/3] hwrng: bcm2835: add " Álvaro Fernández Rojas
2021-03-05 8:07 ` Philipp Zabel
2021-03-08 22:00 ` Florian Fainelli
2021-03-12 13:14 ` [PATCH v6 0/3] " Herbert Xu
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=20210305070132.2986-2-noltari@gmail.com \
--to=noltari@gmail.com \
--cc=alexandru.ardelean@analog.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=lee.jones@linaro.org \
--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=mpm@selenic.com \
--cc=nsaenzjulienne@suse.de \
--cc=p.zabel@pengutronix.de \
--cc=rikard.falkeborn@gmail.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=stefan.wahren@i2se.com \
--cc=tiantao6@hisilicon.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).