From: Rob Herring <robh@kernel.org>
To: "Álvaro Fernández Rojas" <noltari@gmail.com>
Cc: linux-crypto@vger.kernel.org,
Philipp Zabel <p.zabel@pengutronix.de>,
Matt Mackall <mpm@selenic.com>,
linux-arm-kernel@lists.infradead.org,
Alexandru Ardelean <alexandru.ardelean@analog.com>,
Tian Tao <tiantao6@hisilicon.com>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-rpi-kernel@lists.infradead.org, Ray Jui <rjui@broadcom.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Rikard Falkeborn <rikard.falkeborn@gmail.com>,
devicetree@vger.kernel.org,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Scott Branden <sbranden@broadcom.com>,
Stefan Wahren <stefan.wahren@i2se.com>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Lee Jones <lee.jones@linaro.org>,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH v6 1/3] dt-bindings: rng: bcm2835: add clock constraints
Date: Mon, 8 Mar 2021 14:52:38 -0700 [thread overview]
Message-ID: <20210308215238.GA3018261@robh.at.kernel.org> (raw)
In-Reply-To: <20210305070132.2986-2-noltari@gmail.com>
On Fri, 05 Mar 2021 08:01:30 +0100, Álvaro Fernández Rojas wrote:
> 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(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-08 21:54 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 ` [PATCH v6 1/3] dt-bindings: rng: bcm2835: add clock constraints Álvaro Fernández Rojas
2021-03-08 21:52 ` Rob Herring [this message]
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=20210308215238.GA3018261@robh.at.kernel.org \
--to=robh@kernel.org \
--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=noltari@gmail.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).