brcm,bcm6368-rng controllers require resetting the IPSEC clock in order to get
a functional RNG.
Signed-off-by: Álvaro Fernández Rojas
---
v6: fix dt-bindings warnings.
v5: no changes.
v4: pass dt_binding_check.
v3: make resets required if brcm,bcm6368-rng.
v2: document reset support.
.../devicetree/bindings/rng/brcm,bcm2835.yaml | 11 +++
1 file changed, 11 insertions(+)
diff --git a/Documentation/devicetree/bindings/rng/brcm,bcm2835.yaml
b/Documentation/devicetree/bindings/rng/brcm,bcm2835.yaml
index 5174492e22f3..6da674666d45 100644
--- a/Documentation/devicetree/bindings/rng/brcm,bcm2835.yaml
+++ b/Documentation/devicetree/bindings/rng/brcm,bcm2835.yaml
@@ -28,6 +28,12 @@ properties:
clock-names:
const: ipsec
+ resets:
+maxItems: 1
+
+ reset-names:
+const: ipsec
+
interrupts:
maxItems: 1
@@ -44,6 +50,8 @@ then:
required:
- clocks
- clock-names
+- resets
+- reset-names
additionalProperties: false
@@ -68,4 +76,7 @@ examples:
clocks = <&periph_clk 18>;
clock-names = "ipsec";
+
+resets = <&periph_rst 4>;
+reset-names = "ipsec";
};
--
2.20.1