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>
---
v2:
        - rename this binding
        - rewrite the description

 .../bindings/clock/{corenet-clock.txt => qoriq-clock.txt}      | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)
 rename Documentation/devicetree/bindings/clock/{corenet-clock.txt => 
qoriq-clock.txt} (95%)

diff --git a/Documentation/devicetree/bindings/clock/corenet-clock.txt 
b/Documentation/devicetree/bindings/clock/qoriq-clock.txt
similarity index 95%
rename from Documentation/devicetree/bindings/clock/corenet-clock.txt
rename to Documentation/devicetree/bindings/clock/qoriq-clock.txt
index 24711af..5666812 100644
--- a/Documentation/devicetree/bindings/clock/corenet-clock.txt
+++ b/Documentation/devicetree/bindings/clock/qoriq-clock.txt
@@ -7,6 +7,14 @@ which can then be passed to a variety of internal logic, 
including
 cores and peripheral IP blocks.
 Please refer to the Reference Manual for details.
 
+All references to "1.0" and "2.0" refer to the QorIQ chassis version to
+which the chip complies.
+
+Chassis Version                Example Chips
+---------------                -------------
+1.0                    p4080, p5020, p5040
+2.0                    t4240, b4860, t1040
+
 1. Clock Block Binding
 
 Required properties:
@@ -85,7 +93,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.5

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

Reply via email to