From: Krzysztof Kozlowski Properties varying per variant of the device should still have the broadest constraints set in the top level, so add such for the "resets". Since top-level part says "reset-names" cannot accept one item, disallow it for the two variants which do not use it in practice. Signed-off-by: Krzysztof Kozlowski Reviewed-by: Rob Herring (Arm) Reviewed-by: Biju Das Link: https://patch.msgid.link/20261001060825.53335-2-krzysztof.kozlowski@oss.qualcomm.com Signed-off-by: Marc Kleine-Budde --- .../devicetree/bindings/net/can/renesas,rcar-canfd.yaml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/Documentation/devicetree/bindings/net/can/renesas,rcar-canfd.yaml b/Documentation/devicetree/bindings/net/can/renesas,rcar-canfd.yaml index bbaaef8f4282..1a7a9ce45e97 100644 --- a/Documentation/devicetree/bindings/net/can/renesas,rcar-canfd.yaml +++ b/Documentation/devicetree/bindings/net/can/renesas,rcar-canfd.yaml @@ -133,7 +133,9 @@ properties: power-domains: maxItems: 1 - resets: true + resets: + minItems: 1 + maxItems: 2 reset-names: items: @@ -209,7 +211,6 @@ allOf: resets: minItems: 2 - maxItems: 2 - if: properties: @@ -231,6 +232,8 @@ allOf: resets: maxItems: 1 + reset-names: false + - if: properties: compatible: @@ -246,7 +249,6 @@ allOf: resets: minItems: 2 - maxItems: 2 - if: properties: -- 2.53.0