On Mon, 2026-01-12 at 14:16 +0000, Peter Griffin wrote:
quoted hunk ↗ jump to hunk
Fix the places that don't have correct alphanumeric ordering. This will
make reasoning about where to add future entries more straightforward.
Signed-off-by: Peter Griffin <peter.griffin@linaro.org>
---
Documentation/devicetree/bindings/clock/google,gs101-clock.yaml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/clock/google,gs101-clock.yaml b/Documentation/devicetree/bindings/clock/google,gs101-
clock.yaml
index 09e679c1a9def03d53b8b493929911ea902a1763..a8176687bb773ae90800b9c256bcccebfdef2e49 100644
--- a/Documentation/devicetree/bindings/clock/google,gs101-clock.yaml
+++ b/Documentation/devicetree/bindings/clock/google,gs101-clock.yaml
@@ -27,13 +27,13 @@ description: |
properties:
compatible:
enum:
- - google,gs101-cmu-top
- google,gs101-cmu-apm
- - google,gs101-cmu-misc
- google,gs101-cmu-hsi0
- google,gs101-cmu-hsi2
+ - google,gs101-cmu-misc
- google,gs101-cmu-peric0
- google,gs101-cmu-peric1
+ - google,gs101-cmu-top
If we keep 'top' at the top as one outlier, it'd reflect that it is the
top unit and all other CMUs are children of it.
quoted hunk ↗ jump to hunk
clocks:
minItems: 1
compatible:
contains:
enum:
- - google,gs101-cmu-top
- google,gs101-cmu-apm
+ - google,gs101-cmu-top
And here.
Either way, I don't mind:
Reviewed-by: André Draszik <andre.draszik@linaro.org>
Cheers,
Andre'