The clock name "fmanclk" was given in the example, but not specified
in the binding itself.  Made clock-names mandatory as otherwise there's
not much point having it.

Added a reference to the fsl,qman and fsl,bman properties proposed
in http://patchwork.ozlabs.org/patch/407034/ and
http://patchwork.ozlabs.org/patch/407035/

Signed-off-by: Scott Wood <scottw...@freescale.com>
---
This patch is on top of http://patchwork.ozlabs.org/patch/390351/

 Documentation/devicetree/bindings/powerpc/fsl/fman.txt | 11 ++++++++---
 1 file changed, 8 insertions(+), 3 deletions(-)

diff --git a/Documentation/devicetree/bindings/powerpc/fsl/fman.txt 
b/Documentation/devicetree/bindings/powerpc/fsl/fman.txt
index da8e5f2..edeea16 100644
--- a/Documentation/devicetree/bindings/powerpc/fsl/fman.txt
+++ b/Documentation/devicetree/bindings/powerpc/fsl/fman.txt
@@ -79,12 +79,12 @@ PROPERTIES
 - clocks
                Usage: required
                Value type: <prop-encoded-array>
-               Definition: phandle for fman clock.
+               Definition: phandle for the fman input clock.
 
 - clock-names
-               usage: optional
+               usage: required
                Value type: <stringlist>
-               Definition: A standard property
+               Definition: "fmanclk" for the fman input clock.
 
 - interrupts
                Usage: required
@@ -104,6 +104,11 @@ PROPERTIES
                "Work Queue (WQ) Channel Assignments in the QMan" section
                in DPAA Reference Manual.
 
+- fsl,qman
+- fsl,bman
+               Usage: required
+               Definition: See soc/fsl/qman.txt and soc/fsl/bman.txt
+
 =============================================================================
 FMan MURAM Node
 
-- 
1.9.1

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

Reply via email to