The Marvell Armada RNG uses the same IP as TI from Inside Secure and is
already using the binding. The only missing part is the
"marvell,armada-8k-rng" compatible string.

Rename the binding to inside-secure,safexcel-eip76.yaml to better
reflect it is multi-vendor, licensed IP and to follow the naming
convention using compatible string.

Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
---
 ...g.yaml => inside-secure,safexcel-eip76.yaml} | 17 +++++++++++------
 1 file changed, 11 insertions(+), 6 deletions(-)
 rename Documentation/devicetree/bindings/rng/{omap_rng.yaml => inside-secure,safexcel-eip76.yaml} (79%)

diff --git a/Documentation/devicetree/bindings/rng/omap_rng.yaml b/Documentation/devicetree/bindings/rng/inside-secure,safexcel-eip76.yaml
similarity index 79%
rename from Documentation/devicetree/bindings/rng/omap_rng.yaml
rename to Documentation/devicetree/bindings/rng/inside-secure,safexcel-eip76.yaml
index c0ac4f68ea54..0877eb44f9ed 100644
--- a/Documentation/devicetree/bindings/rng/omap_rng.yaml
+++ b/Documentation/devicetree/bindings/rng/inside-secure,safexcel-eip76.yaml
@@ -1,20 +1,25 @@
 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
 %YAML 1.2
 ---
-$id: http://devicetree.org/schemas/rng/omap_rng.yaml#
+$id: http://devicetree.org/schemas/rng/inside-secure,safexcel-eip76.yaml#
 $schema: http://devicetree.org/meta-schemas/core.yaml#
 
-title: OMAP SoC and Inside-Secure HWRNG Module
+title: Inside-Secure HWRNG Module
 
 maintainers:
   - Jayesh Choudhary <j-choudhary@ti.com>
 
 properties:
   compatible:
-    enum:
-      - ti,omap2-rng
-      - ti,omap4-rng
-      - inside-secure,safexcel-eip76
+    oneOf:
+      - enum:
+          - ti,omap2-rng
+          - ti,omap4-rng
+          - inside-secure,safexcel-eip76
+      - items:
+          - enum:
+              - marvell,armada-8k-rng
+          - const: inside-secure,safexcel-eip76
 
   ti,hwmods:
     const: rng
-- 
2.45.2

On Mon, Oct 14, 2024 at 01:54:57PM -0500, Rob Herring (Arm) wrote:
> The Marvell Armada RNG uses the same IP as TI from Inside Secure and is
> already using the binding. The only missing part is the
> "marvell,armada-8k-rng" compatible string.
> 
> Rename the binding to inside-secure,safexcel-eip76.yaml to better
> reflect it is multi-vendor, licensed IP and to follow the naming
> convention using compatible string.
> 
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> ---
>  ...g.yaml => inside-secure,safexcel-eip76.yaml} | 17 +++++++++++------
>  1 file changed, 11 insertions(+), 6 deletions(-)
>  rename Documentation/devicetree/bindings/rng/{omap_rng.yaml => inside-secure,safexcel-eip76.yaml} (79%)

Patch applied.  Thanks.
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

On Mon, Oct 14, 2024 at 01:54:57PM -0500, Rob Herring (Arm) wrote:
> The Marvell Armada RNG uses the same IP as TI from Inside Secure and is
> already using the binding. The only missing part is the
> "marvell,armada-8k-rng" compatible string.
> 
> Rename the binding to inside-secure,safexcel-eip76.yaml to better
> reflect it is multi-vendor, licensed IP and to follow the naming
> convention using compatible string.
> 
> Signed-off-by: Rob Herring (Arm) <robh@kernel.org>
> ---
>  ...g.yaml => inside-secure,safexcel-eip76.yaml} | 17 +++++++++++------
>  1 file changed, 11 insertions(+), 6 deletions(-)
>  rename Documentation/devicetree/bindings/rng/{omap_rng.yaml => inside-secure,safexcel-eip76.yaml} (79%)

Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>

Best regards,
Krzysztof