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 3/4 V5] Enable MSI support for MPC8610HPCD board
Date: Fri, 23 May 2008 16:32:47 +0800 [thread overview]
Message-ID: <1211531568-31402-3-git-send-email-Jason.jin@freescale.com> (raw)
In-Reply-To: <1211531568-31402-2-git-send-email-Jason.jin@freescale.com>
This patch enable the MSI on 8610hpcd board.
Through the msi-available-ranges property, All the 256
msi interrupts can be tested on this board.
Signed-off-by: Jason Jin <Jason.jin@freescale.com>
---
In this version:
Add a flag MPIC_BROKEN_FRR_NIRQS in mpic_alloc making the mpic use
irq_count instead of FRR[NIRQ] to initialize the interrupt controller.
So the hwirq num need to be changed.
arch/powerpc/boot/dts/mpc8610_hpcd.dts | 16 ++++++++++++++++
arch/powerpc/platforms/86xx/mpc8610_hpcd.c | 3 ++-
2 files changed, 18 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/boot/dts/mpc8610_hpcd.dts b/arch/powerpc/boot/dts/mpc8610_hpcd.dts
index 08a780d..fa9c297 100644
--- a/arch/powerpc/boot/dts/mpc8610_hpcd.dts
+++ b/arch/powerpc/boot/dts/mpc8610_hpcd.dts
@@ -182,6 +182,22 @@
big-endian;
};
+ msi@41600 {
+ compatible = "fsl,mpc8610-msi", "fsl,mpic-msi";
+ reg = <0x41600 0x80>;
+ msi-available-ranges = <0 0x100>;
+ interrupts = <
+ 0xe0 0
+ 0xe1 0
+ 0xe2 0
+ 0xe3 0
+ 0xe4 0
+ 0xe5 0
+ 0xe6 0
+ 0xe7 0>;
+ interrupt-parent = <&mpic>;
+ };
+
global-utilities@e0000 {
compatible = "fsl,mpc8610-guts";
reg = <0xe0000 0x1000>;
diff --git a/arch/powerpc/platforms/86xx/mpc8610_hpcd.c b/arch/powerpc/platforms/86xx/mpc8610_hpcd.c
index dea1320..eb16208 100644
--- a/arch/powerpc/platforms/86xx/mpc8610_hpcd.c
+++ b/arch/powerpc/platforms/86xx/mpc8610_hpcd.c
@@ -70,7 +70,8 @@ static void __init mpc86xx_hpcd_init_irq(void)
/* Alloc mpic structure and per isu has 16 INT entries. */
mpic1 = mpic_alloc(np, res.start,
- MPIC_PRIMARY | MPIC_WANTS_RESET | MPIC_BIG_ENDIAN,
+ MPIC_PRIMARY | MPIC_WANTS_RESET |
+ MPIC_BIG_ENDIAN | MPIC_BROKEN_FRR_NIRQS,
0, 256, " MPIC ");
BUG_ON(mpic1 == NULL);
--
1.5.4
next prev parent reply other threads:[~2008-05-23 8:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 8:32 [PATCH 1/4 V5] booting-without-of for Freescale MSI Jason Jin
2008-05-23 8:32 ` [PATCH 2/4 V6] MSI support on 83xx/85xx/86xx board Jason Jin
2008-05-23 8:32 ` Jason Jin [this message]
2008-05-23 8:32 ` [PATCH 4/4 V5] Enable MSI support for 85xxds board Jason Jin
2008-05-23 13:06 ` Kumar Gala
2008-05-23 13:05 ` [PATCH 3/4 V5] Enable MSI support for MPC8610HPCD board Kumar Gala
2008-05-23 12:59 ` [PATCH 2/4 V6] MSI support on 83xx/85xx/86xx board Anton Vorontsov
2008-05-23 13:02 ` Kumar Gala
2008-05-23 13:41 ` [PATCH] [POWERPC] fsl_msi: few (mostly cosmetic) fixes Anton Vorontsov
2008-05-24 4:48 ` Kumar Gala
2008-05-23 14:31 ` [PATCH 2/4 V6] MSI support on 83xx/85xx/86xx board Michael Ellerman
2008-05-23 13:06 ` Kumar Gala
2008-05-23 13:05 ` [PATCH 1/4 V5] booting-without-of for Freescale MSI 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=1211531568-31402-3-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).