From: Scott Wood <scottwood@freescale.com>
To: <linuxppc-dev@lists.ozlabs.org>
Cc: Scott Wood <scottwood@freescale.com>,
Igal Liberman <Igal.Liberman@freescale.com>,
Emil Medve <Emilian.Medve@Freescale.com>,
devicetree@vger.kernel.org
Subject: [PATCH] powerpc/fsl: Update fman dt binding with clock name and qbman link
Date: Thu, 6 Nov 2014 21:01:34 -0600 [thread overview]
Message-ID: <1415329294-22011-1-git-send-email-scottwood@freescale.com> (raw)
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 <scottwood@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
reply other threads:[~2014-11-07 3:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1415329294-22011-1-git-send-email-scottwood@freescale.com \
--to=scottwood@freescale.com \
--cc=Emilian.Medve@Freescale.com \
--cc=Igal.Liberman@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).