From: Krzysztof Kozlowski Date: Mon, 12 Jun 2023 09:26:11 +0000 (+0200) Subject: dt-bindings: example-schema: don't use enum as fallback, explain clock-names X-Git-Tag: v6.5-rc1~46^2~34 X-Git-Url: http://git.osdn.net/view?a=commitdiff_plain;h=9e654c047061016cb4a07f5c4f3b1596eb481fa6;p=tomoyo%2Ftomoyo-test1.git dt-bindings: example-schema: don't use enum as fallback, explain clock-names Compatibles with multiple entries should have usually only one fallback compatible thus enum followed by enum is not a common case. Use 'const' as second compatible to show the recommended approach. Explain also when clock-names are not really necessary. Signed-off-by: Krzysztof Kozlowski Link: https://lore.kernel.org/r/20230612092611.12385-1-krzysztof.kozlowski@linaro.org Signed-off-by: Rob Herring --- diff --git a/Documentation/devicetree/bindings/example-schema.yaml b/Documentation/devicetree/bindings/example-schema.yaml index f4eec4c42fb3..a41f9b9a196b 100644 --- a/Documentation/devicetree/bindings/example-schema.yaml +++ b/Documentation/devicetree/bindings/example-schema.yaml @@ -52,8 +52,7 @@ properties: - vendor,soc4-ip - vendor,soc3-ip - vendor,soc2-ip - - enum: - - vendor,soc1-ip + - const: vendor,soc1-ip # additionalItems being false is implied # minItems/maxItems equal to 2 is implied - items: @@ -85,6 +84,9 @@ properties: discouraged. clock-names: + # For single-entry lists in clocks, resets etc., the xxx-names often do not + # bring any value, especially if they copy the IP block name. In such case + # just skip the xxx-names. items: - const: bus