From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: "Miquel Raynal (Schneider Electric)" <miquel.raynal@bootlin.com>
Cc: Olivia Mackall <olivia@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jayesh Choudhary <j-choudhary@ti.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Pascal EBERHARD <pascal.eberhard@se.com>,
linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] hwrng: omap: Enable on Renesas RZ/N1D
Date: Sun, 12 Jul 2026 10:13:30 +0200 [thread overview]
Message-ID: <alNMqvOy5DEz_4nf@shikoro> (raw)
In-Reply-To: <20260710-schneider-v7-2-rc1-eip76-upstream-v2-2-4eab557b0e70@bootlin.com>
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
On Fri, Jul 10, 2026 at 08:20:33PM +0200, Miquel Raynal (Schneider Electric) wrote:
> The Kconfig symbol and associated seem to be badly named as they have
> nothing OMAP specific but instead refer to Inside Secure Safexcel
> devices which have been used in many SoCs from different
> manufacturers (like OMAP, Marvell but also eg. Renesas).
>
> The Renesas RZ/N1D features this IP, so add this architecture to the
> dependency allow list. In practice this dependency list does not seem
> very relevant and could be entirely dropped, given the fact that this IP
> has been implemented by many different vendors and seems to be
> architecture agnostic.
I thought the same. But I am also fine with adding one more:
Reviewed-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-07-12 8:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 18:20 [PATCH v2 0/2] hwrng: Enable EIP-76 on RZ/N1 Miquel Raynal (Schneider Electric)
2026-07-10 18:20 ` [PATCH v2 1/2] dt-bindings: rng: Rename the title of the EIP-76 file Miquel Raynal (Schneider Electric)
2026-07-12 8:09 ` Wolfram Sang
2026-07-10 18:20 ` [PATCH v2 2/2] hwrng: omap: Enable on Renesas RZ/N1D Miquel Raynal (Schneider Electric)
2026-07-12 8:13 ` Wolfram Sang [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=alNMqvOy5DEz_4nf@shikoro \
--to=wsa+renesas@sang-engineering.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=j-choudhary@ti.com \
--cc=krzk+dt@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=olivia@selenic.com \
--cc=pascal.eberhard@se.com \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.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