From: Tang Yuantian <yuantian.t...@freescale.com>

Main changs include:
        - Clarified the clock nodes' version number
        - Fixed a issue in example

Singed-off-by: Tang Yuantian <yuantian.t...@freescale.com>
---
 Documentation/devicetree/bindings/clock/corenet-clock.txt | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/Documentation/devicetree/bindings/clock/corenet-clock.txt 
b/Documentation/devicetree/bindings/clock/corenet-clock.txt
index 24711af..d6cadef 100644
--- a/Documentation/devicetree/bindings/clock/corenet-clock.txt
+++ b/Documentation/devicetree/bindings/clock/corenet-clock.txt
@@ -54,6 +54,8 @@ Required properties:
                It takes parent's clock-frequency as its clock.
        * "fsl,qoriq-sysclk-2.0": for input system clock (v2.0).
                It takes parent's clock-frequency as its clock.
+       Note: v1.0 and v2.0 are clock version which should align to
+       clockgen node's they belong to which is chassis version.
 - #clock-cells: From common clock binding. The number of cells in a
        clock-specifier. Should be <0> for "fsl,qoriq-sysclk-[1,2].0"
        clocks, or <1> for "fsl,qoriq-core-pll-[1,2].0" clocks.
@@ -85,7 +87,7 @@ Example for clock block and clock provider:
                        #clock-cells = <0>;
                        compatible = "fsl,qoriq-sysclk-1.0";
                        clock-output-names = "sysclk";
-               }
+               };
 
                pll0: pll0@800 {
                        #clock-cells = <1>;
-- 
1.8.0


_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

Reply via email to