From: Emil Medve <Emilian.Medve@Freescale.com>
To: <scottwood@Freescale.com>, <linuxppc-dev@ozlabs.org>,
<devicetree@vger.kernel.org>
Cc: Emil Medve <Emilian.Medve@Freescale.com>
Subject: [PATCH v5 2/6] dt/bindings: b/qman: Add phandle to the portals
Date: Mon, 8 Dec 2014 04:29:17 -0600 [thread overview]
Message-ID: <1418034561-12034-3-git-send-email-Emilian.Medve@Freescale.com> (raw)
In-Reply-To: <1418034561-12034-1-git-send-email-Emilian.Medve@Freescale.com>
This supports SoC(s) with multiple B/QMan instances
Signed-off-by: Emil Medve <Emilian.Medve@Freescale.com>
---
Documentation/devicetree/bindings/soc/fsl/bman.txt | 10 ++++++++++
Documentation/devicetree/bindings/soc/fsl/qman.txt | 10 ++++++++++
2 files changed, 20 insertions(+)
diff --git a/Documentation/devicetree/bindings/soc/fsl/bman.txt b/Documentation/devicetree/bindings/soc/fsl/bman.txt
index ee03ef2..47ac834 100644
--- a/Documentation/devicetree/bindings/soc/fsl/bman.txt
+++ b/Documentation/devicetree/bindings/soc/fsl/bman.txt
@@ -36,6 +36,11 @@ are located at offsets 0xbf8 and 0xbfc
Value type: <prop-encoded-array>
Definition: Standard property. The error interrupt
+- fsl,bman-portals
+ Usage: Required
+ Value type: <phandle>
+ Definition: Phandle to this BMan instance's portals
+
- fsl,liodn
Usage: See pamu.txt
Value type: <prop-encoded-array>
@@ -104,6 +109,10 @@ The example below shows a BMan FBPR dynamic allocation memory node
The example below shows a (P4080) BMan CCSR-space node
+ bportals: bman-portals@ff4000000 {
+ ...
+ };
+
crypto@300000 {
...
fsl,bman = <&bman, 2>;
@@ -115,6 +124,7 @@ The example below shows a (P4080) BMan CCSR-space node
reg = <0x31a000 0x1000>;
interrupts = <16 2 1 2>;
fsl,liodn = <0x17>;
+ fsl,bman-portals = <&bportals>;
memory-region = <&bman_fbpr>;
};
diff --git a/Documentation/devicetree/bindings/soc/fsl/qman.txt b/Documentation/devicetree/bindings/soc/fsl/qman.txt
index f3da91e..556ebb8 100644
--- a/Documentation/devicetree/bindings/soc/fsl/qman.txt
+++ b/Documentation/devicetree/bindings/soc/fsl/qman.txt
@@ -38,6 +38,11 @@ are located at offsets 0xbf8 and 0xbfc
Value type: <prop-encoded-array>
Definition: Standard property. The error interrupt
+- fsl,qman-portals
+ Usage: Required
+ Value type: <phandle>
+ Definition: Phandle to this QMan instance's portals
+
- fsl,liodn
Usage: See pamu.txt
Value type: <prop-encoded-array>
@@ -127,6 +132,10 @@ The example below shows a QMan FQD and a PFDR dynamic allocation memory nodes
The example below shows a (P4080) QMan CCSR-space node
+ qportals: qman-portals@ff4200000 {
+ ...
+ };
+
clockgen: global-utilities@e1000 {
...
sysclk: sysclk {
@@ -154,6 +163,7 @@ The example below shows a (P4080) QMan CCSR-space node
reg = <0x318000 0x1000>;
interrupts = <16 2 1 3>
fsl,liodn = <0x16>;
+ fsl,qman-portals = <&qportals>;
memory-region = <&qman_fqd &qman_pfdr>;
clocks = <&platform_pll 1>;
};
--
2.2.0
next prev parent reply other threads:[~2014-12-08 10:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 10:29 [PATCH v5 0/6] powerpc/mpc85xx: Add FSL QorIQ DPAA B/QMan support to device tree(s) Emil Medve
2014-12-08 10:29 ` [PATCH v5 1/6] dt/bindings: b/qman: Fix the alloc-ranges in the example(s) Emil Medve
2014-12-08 10:29 ` Emil Medve [this message]
2014-12-08 10:29 ` [PATCH v5 3/6] powerpc/mpc85xx: Create dts components for the FSL QorIQ DPAA BMan Emil Medve
2014-12-08 10:29 ` [PATCH v5 4/6] powerpc/mpc85xx: Create dts components for the FSL QorIQ DPAA QMan Emil Medve
2014-12-08 10:29 ` [PATCH v5 5/6] powerpc/mpc85xx: Add FSL QorIQ DPAA BMan support to device tree(s) Emil Medve
2015-01-30 5:03 ` [v5, " Scott Wood
2015-01-30 14:13 ` Emil Medve
2014-12-08 10:29 ` [PATCH v5 6/6] powerpc/mpc85xx: Add FSL QorIQ DPAA QMan " Emil Medve
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=1418034561-12034-3-git-send-email-Emilian.Medve@Freescale.com \
--to=emilian.medve@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@Freescale.com \
/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).