* [PATCH] dt-bindings: fix warnings in validation of qcom,gcc.yaml
@ 2020-01-22 13:57 Dafna Hirschfeld
2020-01-23 14:26 ` Rob Herring
2020-01-28 18:26 ` Stephen Boyd
0 siblings, 2 replies; 3+ messages in thread
From: Dafna Hirschfeld @ 2020-01-22 13:57 UTC (permalink / raw)
To: linux-arm-msm
Cc: agross, bjorn.andersson, mturquette, sboyd, robh+dt,
mark.rutland, devicetree, linux-kernel, dafna.hirschfeld,
helen.koike, ezequiel, kernel, dafna3
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 <dafna.hirschfeld@collabora.com>
---
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
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] dt-bindings: fix warnings in validation of qcom,gcc.yaml
2020-01-22 13:57 [PATCH] dt-bindings: fix warnings in validation of qcom,gcc.yaml Dafna Hirschfeld
@ 2020-01-23 14:26 ` Rob Herring
2020-01-28 18:26 ` Stephen Boyd
1 sibling, 0 replies; 3+ messages in thread
From: Rob Herring @ 2020-01-23 14:26 UTC (permalink / raw)
To: Dafna Hirschfeld
Cc: linux-arm-msm, Andy Gross, Bjorn Andersson, Michael Turquette,
Stephen Boyd, Mark Rutland, devicetree, linux-kernel,
Helen Koike, Ezequiel Garcia, Collabora Kernel ML, dafna3
On Wed, Jan 22, 2020 at 7:57 AM Dafna Hirschfeld
<dafna.hirschfeld@collabora.com> 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 <dafna.hirschfeld@collabora.com>
Fixes: d109ea0970cf ("dt-bindings: clock: Document external clocks for
MSM8998 gcc")
Acked-by: Rob Herring <robh@kernel.org>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] dt-bindings: fix warnings in validation of qcom,gcc.yaml
2020-01-22 13:57 [PATCH] dt-bindings: fix warnings in validation of qcom,gcc.yaml Dafna Hirschfeld
2020-01-23 14:26 ` Rob Herring
@ 2020-01-28 18:26 ` Stephen Boyd
1 sibling, 0 replies; 3+ messages in thread
From: Stephen Boyd @ 2020-01-28 18:26 UTC (permalink / raw)
To: Dafna Hirschfeld, linux-arm-msm
Cc: agross, bjorn.andersson, mturquette, robh+dt, mark.rutland,
devicetree, linux-kernel, dafna.hirschfeld, helen.koike,
ezequiel, kernel, dafna3
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 <dafna.hirschfeld@collabora.com>
> ---
Applied to clk-next
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-01-28 18:26 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-22 13:57 [PATCH] dt-bindings: fix warnings in validation of qcom,gcc.yaml Dafna Hirschfeld
2020-01-23 14:26 ` Rob Herring
2020-01-28 18:26 ` Stephen Boyd
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).