Skip to contentSkip to conversation

dt-bindings: rng: omap_rng: Drop requirement for clocks

PATCH Applied Andrew Davis 2 participants 2 messages Sep 1, 2022 – Sep 7, 2022

Subsystems (3)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 dt-bindings: rng: omap_rng: Drop requirement for clocks

For K3 devices the clock fed into the RNG module is shared with the rest of the Crypto module, it is not dedicated to the RNG module and cannot be controlled by the RNG driver. The driver does not require this clock to always be defined and the DT binding should not force it either.

Remove this so we can start dropping out the clock properties as needed.

---
 Documentation/devicetree/bindings/rng/omap_rng.yaml | 11 -----------
 1 file changed, 11 deletions(-)
Documentation/devicetree/bindings/rng/omap_rng.yaml +0 -11
index 010188cdbec86..ccf54fae83028 100644
@@ -53,17 +53,6 @@ allOf:
       required:
         - interrupts
 
-  - if:
-      properties:
-        compatible:
-          contains:
-            enum:
-              - inside-secure,safexcel-eip76
-
-    then:
-      required:
-        - clocks
-
 
 required:
   - compatible
Signature · 1 line
2.36.1
maintainer Applied
#1 lore raw
Quoted 5 lines · Andrew Davis

For K3 devices the clock fed into the RNG module is shared with the rest of the Crypto module, it is not dedicated to the RNG module and cannot be controlled by the RNG driver. The driver does not require this clock to always be defined and the DT binding should not force it either.

Quoted 7 lines

Remove this so we can start dropping out the clock properties as needed.

---
 Documentation/devicetree/bindings/rng/omap_rng.yaml | 11 -----------
 1 file changed, 11 deletions(-)

Applied, thanks!