From: Kumar Gala <galak@kernel.crashing.org>
To: linuxppc-dev@ozlabs.org
Subject: [PATCH 2/3] [POWERPC] Add docs for Freescale RapidIO device tree node
Date: Tue, 20 Nov 2007 23:13:58 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.64.0711202313350.24220@blarg.am.freescale.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0711202310280.24220@blarg.am.freescale.net>
---
Documentation/powerpc/booting-without-of.txt | 47 ++++++++++++++++++++++++--
1 files changed, 44 insertions(+), 3 deletions(-)
diff --git a/Documentation/powerpc/booting-without-of.txt b/Documentation/powerpc/booting-without-of.txt
index eb14dd5..3d959d6 100644
--- a/Documentation/powerpc/booting-without-of.txt
+++ b/Documentation/powerpc/booting-without-of.txt
@@ -2521,9 +2521,9 @@ platforms are moved over to use the flattened-device-tree model.
Required properties:
- compatible : compatible list, contains 2 entries, first is
- "fsl,sata-CHIP", where CHIP is the processor
+ "fsl,CHIP-sata", where CHIP is the processor
(mpc8315, mpc8379, etc.) and the second is
- "fsl,sata-pq2pro"
+ "fsl,pq2pro-sata"
- interrupts : <interrupt mapping for SATA IRQ>
- interrupt-parent : optional, if needed for interrupt mapping
- reg : <registers mapping>
@@ -2531,12 +2531,53 @@ platforms are moved over to use the flattened-device-tree model.
Example:
sata@19000 {
- compatible = "fsl,mpc8315-sata", "fsl,sata-pq2pro;
+ compatible = "fsl,mpc8315-sata", "fsl,pq2pro-sata;
reg = <19000 1000>;
interrupts = <2d 8>;
interrupt-parent = < &ipic >;
};
+ * Frescale Serial RapidIO bus controller
+
+ RapidIO is a definition of a system interconnect. This node add
+ the support for RapidIO processor in kernel. The node name is
+ suggested to be 'rapidio'.
+
+ Required properties:
+
+ - compatible : compatible list, contains 2 entries, first is
+ "fsl,CHIP-rapidio", where CHIP is the processor
+ (mpc8572, mpc8641, etc.) and the second is
+ "fsl,delta-rapidio"
+ - interrupts : interrupts are expected in the following
+ order:
+ * Error/port write
+ * Outbound Doorbell
+ * Inbound Doorbell
+ * Outbound Msg Unit 1
+ * Inbound Msg Unit 1
+ * Outbound Msg Unit 2
+ * Inbound Msg Unit 2
+ - interrupt-parent : optional, if needed for interrupt mapping
+ - reg : <registers mapping>
+ - #address-cells : Should always be 2
+ - #size--cells : Should always be 2
+ - ranges : Details processor physical addr to RapidIO address
+
+ Example:
+
+ rapidio@c0000 {
+ compatible = "fsl,mpc8641-rapidio", "fsl,delta-rapidio;
+ #address-cells = <2>;
+ #size-cells = <2>;
+ reg = <c0000 20000>;
+ ranges = <0 0 c0000000 20000000>;
+ interrupt-parent = <&mpic>;
+ /* err_irq bell_outb_irq bell_inb_irq msg1_tx_irq msg1_rx_irq
+ msg2_tx_irq msg2_rx_irq */
+ interrupts = <30 2 31 2 32 2 35 2 36 2 37 2 38 2>;
+ };
+
More devices will be defined as this spec matures.
VII - Specifying interrupt information for devices
--
1.5.3.4
next prev parent reply other threads:[~2007-11-21 5:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 5:11 [PATCH 0/3] Device tree docs updates for FSL periphs Kumar Gala
2007-11-21 5:12 ` [PATCH 1/3] [POWERPC] Add docs for Freescale 83xx SATA device tree nodes Kumar Gala
2007-11-25 22:22 ` Arnd Bergmann
2007-11-26 15:41 ` Kumar Gala
2007-11-26 16:06 ` Arnd Bergmann
2007-12-03 2:37 ` Li Yang
2007-11-21 5:13 ` Kumar Gala [this message]
2007-11-21 17:29 ` [PATCH 2/3] [POWERPC] Add docs for Freescale RapidIO device tree node Scott Wood
2007-11-21 19:20 ` Kumar Gala
2007-11-21 5:14 ` [PATCH 3/3] [POWERPC] Add docs for Freescale DMA & DMA channel device tree nodes Kumar Gala
2007-11-21 14:59 ` Timur Tabi
2007-11-21 15:33 ` Kumar Gala
2007-11-21 17:35 ` Scott Wood
2007-11-21 19:21 ` Kumar Gala
2007-11-21 19:27 ` Scott Wood
2007-11-21 22:28 ` David Gibson
2007-11-22 0:51 ` Timur Tabi
2007-11-26 15:44 ` Scott Wood
2007-11-22 0:49 ` Timur Tabi
2007-11-22 0:48 ` Timur Tabi
2007-11-21 17:33 ` Scott Wood
2007-11-21 19:19 ` Kumar Gala
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=Pine.LNX.4.64.0711202313350.24220@blarg.am.freescale.net \
--to=galak@kernel.crashing.org \
--cc=linuxppc-dev@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).