From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Jonathan McDowell <noodles@earth.li>
Cc: Andy Gross <agross@kernel.org>, Rob Herring <robh+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: qcom: add prng definition to ipq806x
Date: Fri, 22 Jan 2021 12:37:06 -0600 [thread overview]
Message-ID: <YAsbUsLuDuDiqwFU@builder.lan> (raw)
In-Reply-To: <20201129185022.GT32650@earth.li>
On Sun 29 Nov 12:50 CST 2020, Jonathan McDowell wrote:
> Gentle poke; did this just get missed or is there some reason not to
> apply it?
>
There's no reason why this wasn't applied. I've picked it up now.
Thank you,
Bjorn
> On Sun, Jul 05, 2020 at 03:25:44PM +0100, Jonathan McDowell wrote:
> > Add missing prng definition for ipq806x SoC
> >
> > Signed-off-by: Jonathan McDowell <noodles@earth.li>
> > ---
> > arch/arm/boot/dts/qcom-ipq8064.dtsi | 7 +++++++
> > 1 file changed, 7 insertions(+)
> >
> > diff --git a/arch/arm/boot/dts/qcom-ipq8064.dtsi b/arch/arm/boot/dts/qcom-ipq8064.dtsi
> > index b912da9a3ff3..22e0669b9133 100644
> > --- a/arch/arm/boot/dts/qcom-ipq8064.dtsi
> > +++ b/arch/arm/boot/dts/qcom-ipq8064.dtsi
> > @@ -386,6 +386,13 @@ gsbi7_serial: serial@16640000 {
> > };
> > };
> >
> > + rng@1a500000 {
> > + compatible = "qcom,prng";
> > + reg = <0x1a500000 0x200>;
> > + clocks = <&gcc PRNG_CLK>;
> > + clock-names = "core";
> > + };
> > +
> > sata_phy: sata-phy@1b400000 {
> > compatible = "qcom,ipq806x-sata-phy";
> > reg = <0x1b400000 0x200>;
> > --
> > 2.27.0
> >
>
> J.
>
> --
> Revd Jonathan McDowell, ULC | Hail Eris. All hail Discordia. Fnord?
prev parent reply other threads:[~2021-01-22 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 14:25 [PATCH] ARM: dts: qcom: add prng definition to ipq806x Jonathan McDowell
2020-11-29 18:50 ` Jonathan McDowell
2021-01-22 18:37 ` Bjorn Andersson [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=YAsbUsLuDuDiqwFU@builder.lan \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=noodles@earth.li \
--cc=robh+dt@kernel.org \
/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).