Commit 9e654c04 authored by Krzysztof Kozlowski's avatar Krzysztof Kozlowski Committed by Rob Herring
Browse files

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: default avatarKrzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Link: https://lore.kernel.org/r/20230612092611.12385-1-krzysztof.kozlowski@linaro.org


Signed-off-by: default avatarRob Herring <robh@kernel.org>
parent 0f8e5651

Documentation/devicetree/bindings/example-schema.yaml

+4 −2
Original line number Diff line number Diff line
@@ -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