From: Shaveta Leekha <shaveta@freescale.com>
To: <devicetree-discuss@lists.ozlabs.org>, <linuxppc-dev@lists.ozlabs.org>
Cc: Shaveta Leekha <shaveta@freescale.com>
Subject: [PATCH] Add device file bindings for MAPLE
Date: Sat, 27 Jul 2013 18:33:42 +0530 [thread overview]
Message-ID: <1374930222-32739-1-git-send-email-shaveta@freescale.com> (raw)
Signed-off-by: Shaveta Leekha <shaveta@freescale.com>
---
.../devicetree/bindings/powerpc/fsl/maple.txt | 50 ++++++++++++++++++++
1 files changed, 50 insertions(+), 0 deletions(-)
create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/maple.txt
diff --git a/Documentation/devicetree/bindings/powerpc/fsl/maple.txt b/Documentation/devicetree/bindings/powerpc/fsl/maple.txt
new file mode 100644
index 0000000..23b80a7
--- /dev/null
+++ b/Documentation/devicetree/bindings/powerpc/fsl/maple.txt
@@ -0,0 +1,50 @@
+* Freescale MAPLE Multi Accelerator Platform Engine Baseband 3
+ (MAPLE-B3)device nodes
+
+Supported chips:
+Example: B4860
+
+Required properties:
+
+- compatible: Should contain "fsl,maple-b3" as the value
+ This identifies Multi Accelerator Platform Engine
+ Baseband 3 block.
+
+- reg: offset and length of the register set for the device
+
+- interrupts
+ Usage: required
+ Value type: <prop_encoded-array>
+ Definition: Specifies the interrupts generated by this device. The
+ value of the interrupts property consists of one interrupt
+ specifier. The format of the specifier is defined by the
+ binding document describing the node's interrupt parent.
+
+ A single IRQ that handles error conditions is specified by
+ this property. (Typically shared with port-write).
+
+Devices that have LIODNs need to specify links to the parent PAMU controller
+(the actual PAMU controller that this device is connected to) and a pointer to
+the LIODN register, if applicable.
+
+- fsl,iommu-parent
+ : <phandle>
+ This property should be present
+
+- status = "disabled"
+ In this example, status is set "disabled",
+ As Maple device wouldn't be used by PPC Linux. This representation is required
+ for doing the PAMU programming on the Linux side.
+
+Example:
+ /* B4860 */
+
+ maple@800000 {
+ #address-cells = <0>;
+ #size-cells = <0>;
+ status = "disabled";
+ compatible = "fsl,maple-b3";
+ reg = <0x8000000 0x10000>;
+ interrupts = <16 2 1 18>;
+ fsl,iommu-parent = <&pamu1>;
+ };
--
1.7.6.GIT
next reply other threads:[~2013-07-27 13:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-27 13:03 Shaveta Leekha [this message]
2013-07-30 0:00 ` [PATCH] Add device file bindings for MAPLE Scott Wood
2013-07-30 0:29 ` Benjamin Herrenschmidt
2013-07-30 5:37 ` Leekha Shaveta-B20052
-- strict thread matches above, loose matches on Subject: below --
2013-08-01 11:02 Shaveta Leekha
2013-08-01 16:05 ` Kumar Gala
2013-08-05 21:11 ` Scott Wood
2013-08-05 22:26 ` Kumar Gala
2013-08-05 22:16 ` Scott Wood
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=1374930222-32739-1-git-send-email-shaveta@freescale.com \
--to=shaveta@freescale.com \
--cc=devicetree-discuss@lists.ozlabs.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).