linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jason Jin <Jason.jin@freescale.com>
To: galak@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org, Jason Jin <Jason.jin@freescale.com>
Subject: [PATCH 4/4] booting-without-of for Freescale MSI
Date: Mon,  5 May 2008 15:47:14 +0800	[thread overview]
Message-ID: <1209973634-1699-4-git-send-email-Jason.jin@freescale.com> (raw)
In-Reply-To: <1209973634-1699-3-git-send-email-Jason.jin@freescale.com>

Binding document adding for Freescale MSI support.

Signed-off-by: Jason Jin <Jason.jin@freescale.com>
---
 Documentation/powerpc/booting-without-of.txt |   37 +++++++++++++++++++++++++-
 1 files changed, 36 insertions(+), 1 deletions(-)

diff --git a/Documentation/powerpc/booting-without-of.txt b/Documentation/powerpc/booting-without-of.txt
index 1d2a772..9c496f6 100644
--- a/Documentation/powerpc/booting-without-of.txt
+++ b/Documentation/powerpc/booting-without-of.txt
@@ -57,7 +57,10 @@ Table of Contents
       n) 4xx/Axon EMAC ethernet nodes
       o) Xilinx IP cores
       p) Freescale Synchronous Serial Interface
-	  q) USB EHCI controllers
+      q) USB EHCI controllers
+      r) Freescale Display Interface Unit
+      s) Freescale on board FPGA
+      t) Freescael MSI interrupt controller
 
   VII - Marvell Discovery mv64[345]6x System Controller chips
     1) The /system-controller node
@@ -2870,6 +2873,38 @@ platforms are moved over to use the flattened-device-tree model.
 		reg = <0xe8000000 32>;
 	};
 
+    t) Freescale MSI interrupt controller
+
+    Reguired properities:
+    - compatible : should be "fsl,MPIC-MSI" for 85xx/86xx cpu,
+      and "fsl,IPIC-MSI" for 83xx cpu.
+    - reg : should contain the address and the length of the shared message
+      interrupt register set.
+    - msi-available-ranges: use <start count> style section to define which
+      msi interrupt can be used in the 256 msi interrupts.
+    - interrupts : should contain the msi interrupts cascade to the host
+      interrupt controller.
+    - interrupt-parent: should be "&mpic" for 85xx/86xx cpu and "&ipic"
+      for 83xx cpu.
+
+    Example (85xx/86xx)
+	msi@41600 {
+		compatible = "fsl,MPIC-MSI";
+		reg = <0x41600 0x80>;
+		msi-available-ranges = <0 0x100>;
+		interrupts = <
+			0xb0 0
+			0xb1 0
+			0xb2 0
+			0xb3 0
+			0xb4 0
+			0xb5 0
+			0xb6 0
+			0xb7 0>;
+		interrupt-parent = <&mpic>;
+	};
+
+
 VII - Marvell Discovery mv64[345]6x System Controller chips
 ===========================================================
 
-- 
1.5.4

  reply	other threads:[~2008-05-05  7:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05  7:47 [PATCH 1/4 V3] MSI support on 83xx/85xx/86xx board Jason Jin
2008-05-05  7:47 ` [PATCH 2/4 V2] Enable MSI support for MPC8610HPCD board Jason Jin
2008-05-05  7:47   ` [PATCH 3/4] Enable MSI support for 85xxds board Jason Jin
2008-05-05  7:47     ` Jason Jin [this message]
2008-05-05 18:00       ` [PATCH 4/4] booting-without-of for Freescale MSI Segher Boessenkool
2008-05-06  9:23         ` Jin Zhengxiong
2008-05-06 10:44           ` Segher Boessenkool
2008-05-07  9:35             ` Jin Zhengxiong
2008-05-05 11:24 ` [PATCH 1/4 V3] MSI support on 83xx/85xx/86xx board Michael Ellerman
2008-05-06  9:23   ` Jin Zhengxiong

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=1209973634-1699-4-git-send-email-Jason.jin@freescale.com \
    --to=jason.jin@freescale.com \
    --cc=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).