Message ID | 20230606144447.775942-1-alexander.stein@ew.tq-group.com |
---|---|
State | Accepted |
Commit | cb60fdf6e23068e0954b2a66855b7dc5d6019a87 |
Headers | show |
Series | [1/1] dt-bindings: phy: mixel,mipi-dsi-phy: Remove assigned-clock* properties | expand |
diff --git a/Documentation/devicetree/bindings/phy/mixel,mipi-dsi-phy.yaml b/Documentation/devicetree/bindings/phy/mixel,mipi-dsi-phy.yaml index 786cfd71cb7eb..3c28ec50f0979 100644 --- a/Documentation/devicetree/bindings/phy/mixel,mipi-dsi-phy.yaml +++ b/Documentation/devicetree/bindings/phy/mixel,mipi-dsi-phy.yaml @@ -32,15 +32,6 @@ properties: clock-names: const: phy_ref - assigned-clocks: - maxItems: 1 - - assigned-clock-parents: - maxItems: 1 - - assigned-clock-rates: - maxItems: 1 - "#phy-cells": const: 0
These properties are allowed anyway and some SoC (e.g. imx8mq) configure more than just one clock using these properties. Fixes: f9b0593dd4fc6 ("dt-bindings: phy: Convert mixel,mipi-dsi-phy to json-schema") Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com> --- I can't reproduce the mentioned mis-matches in commit f9b0593dd4fc6 ("dt-bindings: phy: Convert mixel,mipi-dsi-phy to json-schema"). Since commit 62270eeb2b639 ("arm64: dts: imx8mq: Add clock parents for mipi dphy") imx8mq.dtsi configures several clocks using assigned-clocks* properties. .../devicetree/bindings/phy/mixel,mipi-dsi-phy.yaml | 9 --------- 1 file changed, 9 deletions(-)