[PATCH v2 0/2] hwrng: Enable EIP-76 on RZ/N1

[PATCH v2 0/2] hwrng: Enable EIP-76 on RZ/N1

[Miquel Raynal (Schneider Electric)]

The EIP-76 is an block from Inside-Secure which is not at all OMAP
specific. Make it available on Renesas RZ/N1 where it is present inside
a container named EIP-150.

These patches come from a bigger series which I split into meaningful
patchsets, one per subsystem:

Link: https://lore.kernel.org/all/20260327-schneider-v7-0-rc1-crypto-v1-0-5e6ff7853994@bootlin.com/

Changes in v2:
- Patches have been extracted from the bigger series.
- Rebased on top of v7.2-rc1.
- Tag from Rob collected.

Signed-off-by: Miquel Raynal (Schneider Electric) <miquel.raynal@bootlin.com>
---
Miquel Raynal (Schneider Electric) (2):
      dt-bindings: rng: Rename the title of the EIP-76 file
      hwrng: omap: Enable on Renesas RZ/N1D

 Documentation/devicetree/bindings/rng/inside-secure,safexcel-eip76.yaml | 2 +-
 drivers/char/hw_random/Kconfig                                          | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
---
base-commit: 7f26e010764df304602f33912a0550dcf46e72c2
change-id: 20260710-schneider-v7-2-rc1-eip76-upstream-4d6a83015f7e

Best regards,
-- 
Miquel Raynal (Schneider Electric) <miquel.raynal@bootlin.com>

[PATCH v2 1/2] dt-bindings: rng: Rename the title of the EIP-76 file

[Miquel Raynal (Schneider Electric)]

Be a little more precise in the title by giving the family name and the
own name of the hardware block. Despite the original compatibles, this
file describes a SafeXcel EIP-76 hardware random number generator.

Signed-off-by: Miquel Raynal (Schneider Electric) <miquel.raynal@bootlin.com>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
---
 Documentation/devicetree/bindings/rng/inside-secure,safexcel-eip76.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/rng/inside-secure,safexcel-eip76.yaml b/Documentation/devicetree/bindings/rng/inside-secure,safexcel-eip76.yaml
index f501fc7691c6..92d906998211 100644
--- a/Documentation/devicetree/bindings/rng/inside-secure,safexcel-eip76.yaml
+++ b/Documentation/devicetree/bindings/rng/inside-secure,safexcel-eip76.yaml
@@ -4,7 +4,7 @@
 $id: http://devicetree.org/schemas/rng/inside-secure,safexcel-eip76.yaml#
 $schema: http://devicetree.org/meta-schemas/core.yaml#
 
-title: Inside-Secure HWRNG Module
+title: Inside-Secure SafeXcel EIP-76 HWRNG Module
 
 maintainers:
   - Jayesh Choudhary <j-choudhary@ti.com>

-- 
2.54.0

Re: [PATCH v2 1/2] dt-bindings: rng: Rename the title of the EIP-76 file

[Wolfram Sang]

[-- Attachment #1: Type: text/plain, Size: 523 bytes --]

On Fri, Jul 10, 2026 at 08:20:32PM +0200, Miquel Raynal (Schneider Electric) wrote:
> Be a little more precise in the title by giving the family name and the
> own name of the hardware block. Despite the original compatibles, this
> file describes a SafeXcel EIP-76 hardware random number generator.
> 
> Signed-off-by: Miquel Raynal (Schneider Electric) <miquel.raynal@bootlin.com>
> Acked-by: Rob Herring (Arm) <robh@kernel.org>

Yes, more precise.

Acked-by: Wolfram Sang <wsa+renesas@sang-engineering.com>


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[PATCH v2 2/2] hwrng: omap: Enable on Renesas RZ/N1D

[Miquel Raynal (Schneider Electric)]

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.

Signed-off-by: Miquel Raynal (Schneider Electric) <miquel.raynal@bootlin.com>
---
 drivers/char/hw_random/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/char/hw_random/Kconfig b/drivers/char/hw_random/Kconfig
index a5bcef4a54ee..2f1e3a77c948 100644
--- a/drivers/char/hw_random/Kconfig
+++ b/drivers/char/hw_random/Kconfig
@@ -193,7 +193,7 @@ config HW_RANDOM_IXP4XX
 
 config HW_RANDOM_OMAP
 	tristate "OMAP Random Number Generator support"
-	depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS || ARCH_MVEBU || ARCH_K3 || COMPILE_TEST
+	depends on ARCH_OMAP16XX || ARCH_OMAP2PLUS || ARCH_MVEBU || ARCH_K3 || ARCH_RZN1 || COMPILE_TEST
 	default HW_RANDOM
 	help
 	  This driver provides kernel-side support for the Random Number

-- 
2.54.0

Re: [PATCH v2 2/2] hwrng: omap: Enable on Renesas RZ/N1D

[Wolfram Sang]

[-- 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 --]