From: Rob Herring <robh@kernel.org>
To: "Horia Geantă" <horia.geanta@nxp.com>
Cc: Franck Lenormand <franck.lenormand@nxp.com>,
Marco Felsch <m.felsch@pengutronix.de>,
Matt Mackall <mpm@selenic.com>,
Iuliana Prodan <iuliana.prodan@nxp.com>,
linux-crypto@vger.kernel.org, Fabio Estevam <festevam@gmail.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Martin Kaiser <martin@kaiser.cx>,
linux-arm-kernel@lists.infradead.org,
NXP Linux Team <linux-imx@nxp.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, Shawn Guo <shawnguo@kernel.org>,
Silvano Di Ninno <silvano.dininno@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH v3 1/5] dt-bindings: rng: add RNGB compatibles for i.MX6 SoCs
Date: Tue, 14 Jul 2020 15:09:44 -0600 [thread overview]
Message-ID: <20200714210944.GA2921406@bogus> (raw)
In-Reply-To: <20200714123920.23711-2-horia.geanta@nxp.com>
On Tue, 14 Jul 2020 15:39:16 +0300, Horia Geantă wrote:
> RNGB block is found in some i.MX6 SoCs - 6SL, 6SLL, 6ULL, 6ULZ.
> Add corresponding compatible strings.
>
> Note:
>
> Several NXP SoC from QorIQ family (P1010, P1023, P4080, P3041, P5020)
> also have a RNGB, however it's part of the CAAM
> (Cryptograhic Accelerator and Assurance Module) crypto accelerator.
> In this case, RNGB is managed in the caam driver
> (drivers/crypto/caam/), since it's tightly related to
> the caam "job ring" interface, not to mention CAAM internally relying on
> RNGB as source of randomness.
>
> On the other hand, the i.MX6 SoCs with RNGB have a DCP
> (Data Co-Processor) crypto accelerator and this block and RNGB
> are independent.
>
> Signed-off-by: Horia Geantă <horia.geanta@nxp.com>
> ---
> Documentation/devicetree/bindings/rng/imx-rng.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2020-07-14 21:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 12:39 [PATCH v3 0/5] hwrng: add support for i.MX6 rngb Horia Geantă
2020-07-14 12:39 ` [PATCH v3 1/5] dt-bindings: rng: add RNGB compatibles for i.MX6 SoCs Horia Geantă
2020-07-14 21:09 ` Rob Herring [this message]
2020-07-14 12:39 ` [PATCH v3 2/5] ARM: dts: imx6sl: fix rng node Horia Geantă
2020-07-14 12:39 ` [PATCH v3 3/5] ARM: dts: imx6sll: add rng Horia Geantă
2020-07-14 12:39 ` [PATCH v3 4/5] ARM: dts: imx6ull: " Horia Geantă
2020-07-14 12:39 ` [PATCH v3 5/5] hwrng: imx-rngc: enable driver for i.MX6 Horia Geantă
2020-07-14 12:47 ` Arnd Bergmann
2020-07-14 14:27 ` Horia Geantă
2020-07-14 12:48 ` Fabio Estevam
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=20200714210944.GA2921406@bogus \
--to=robh@kernel.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=franck.lenormand@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=iuliana.prodan@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=martin@kaiser.cx \
--cc=mpm@selenic.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=silvano.dininno@nxp.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).