The last example in qcom,gcc.yaml set 'sleep' as the second
value of 'clock-names'. According to the schema is should
be 'sleep_clk'. Fix the example to conform the schema.
This fixes a warning when validating the schema:
"clock-names: ... is not valid under any of the given schemas"
Signed-off-by: Dafna Hirschfeld <[email protected]>
---
I tested this patch on top of the patch
"dt-binding: fix compilation error of the example in qcom,gcc.yaml"
which fixes a compilation error in this file
Documentation/devicetree/bindings/clock/qcom,gcc.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/clock/qcom,gcc.yaml b/Documentation/devicetree/bindings/clock/qcom,gcc.yaml
index 50ff07f80acb..cac1150c9292 100644
--- a/Documentation/devicetree/bindings/clock/qcom,gcc.yaml
+++ b/Documentation/devicetree/bindings/clock/qcom,gcc.yaml
@@ -235,7 +235,7 @@ examples:
<0>,
<0>;
clock-names = "xo",
- "sleep",
+ "sleep_clk",
"usb3_pipe",
"ufs_rx_symbol0",
"ufs_rx_symbol1",
--
2.17.1
On Wed, Jan 22, 2020 at 7:57 AM Dafna Hirschfeld
<[email protected]> wrote:
>
> The last example in qcom,gcc.yaml set 'sleep' as the second
> value of 'clock-names'. According to the schema is should
> be 'sleep_clk'. Fix the example to conform the schema.
> This fixes a warning when validating the schema:
> "clock-names: ... is not valid under any of the given schemas"
>
> Signed-off-by: Dafna Hirschfeld <[email protected]>
Fixes: d109ea0970cf ("dt-bindings: clock: Document external clocks for
MSM8998 gcc")
Acked-by: Rob Herring <[email protected]>
Quoting Dafna Hirschfeld (2020-01-22 05:57:41)
> The last example in qcom,gcc.yaml set 'sleep' as the second
> value of 'clock-names'. According to the schema is should
> be 'sleep_clk'. Fix the example to conform the schema.
> This fixes a warning when validating the schema:
> "clock-names: ... is not valid under any of the given schemas"
>
> Signed-off-by: Dafna Hirschfeld <[email protected]>
> ---
Applied to clk-next