| Message ID | 20220901171041.32056-1-afd@ti.com (mailing list archive) |
|---|---|
| State | Not Applicable |
| Delegated to: | Herbert Xu |
| Headers | show |
| Series | dt-bindings: rng: omap_rng: Drop requirement for clocks | expand |
On Thu, 01 Sep 2022 12:10:41 -0500, Andrew Davis wrote: > 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. > > Signed-off-by: Andrew Davis <afd@ti.com> > --- > Documentation/devicetree/bindings/rng/omap_rng.yaml | 11 ----------- > 1 file changed, 11 deletions(-) > Applied, thanks!
diff --git a/Documentation/devicetree/bindings/rng/omap_rng.yaml b/Documentation/devicetree/bindings/rng/omap_rng.yaml index 010188cdbec86..ccf54fae83028 100644 --- a/Documentation/devicetree/bindings/rng/omap_rng.yaml +++ b/Documentation/devicetree/bindings/rng/omap_rng.yaml @@ -53,17 +53,6 @@ allOf: required: - interrupts - - if: - properties: - compatible: - contains: - enum: - - inside-secure,safexcel-eip76 - - then: - required: - - clocks - required: - compatible
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. Signed-off-by: Andrew Davis <afd@ti.com> --- Documentation/devicetree/bindings/rng/omap_rng.yaml | 11 ----------- 1 file changed, 11 deletions(-)