From: Li Li <r64360@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Phillips Kim <Kim.Phillips@freescale.com>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Jin Zhengxiong <Jason.Jin@freescale.com>,
Li Tony <Tony.Li@freescale.com>, Olof Johansson <olof@lixom.net>
Subject: Re: [PATCH 2/2] powerpc: Add IPIC MSI support
Date: Fri, 14 Dec 2007 17:13:47 +0800 [thread overview]
Message-ID: <1197623627.5016.1.camel@Guyver> (raw)
In-Reply-To: <90B908AC-E879-4046-AAFC-FE79EB78A932@kernel.crashing.org>
On Fri, 2007-12-14 at 16:52 +0800, Kumar Gala wrote:
>=20
> On Dec 14, 2007, at 2:47 AM, Li Tony wrote:
>=20
> >=20
> > Hi,=20
> >=20
> > I think it is possible to make common code to support both IPIC
> and =20
> > MPIC.=20
> > Currently, the MPIC has already implemented MSI which is different =20
> > from IPIC and embedded into the mpic code body.=20
> > If want to unifiy MSI code, we need to remove the current MPIC MSI =20
> > implementation.
>=20
> The MPIC is going to have to support several MSI styles (IBM/U3, =20
> PaSemi, and FSL) since we all seem to handle it differently.
>=20
Yes, you are right. I misunderstands here.
> > Micheal, what is your opinion ??=20
> >=20
> > Jin is working on 86xx msi now.
>=20
> What PCIe cards are you using to test MSIs?
>=20
Intel PRO1000 PCIE network card and SysKonnect card.
> - k
>=20
> >> -----Original Message-----=20
> >> From: Kumar Gala [mailto:galak@kernel.crashing.org]=20
> >> Sent: 2007=E5=B9=B412=E6=9C=8814=E6=97=A5 13:45=20
> >> To: Li Tony=20
> >> Cc: Phillips Kim; michael@ellerman.id.au; linuxppc-dev=20
> >> Subject: Re: [PATCH 2/2] powerpc: Add IPIC MSI support=20
> >>=20
> >>=20
> >> On Dec 4, 2007, at 4:39 AM, Li Li wrote:=20
> >>=20
> >>> Modified based on discussion on list.=20
> >>>=20
> >>> 1. Adopt virq_to_hw routine=20
> >>> 2. Correct a legacy bug=20
> >>>=20
> >>> Implements the IPIC MSI as two level interrupt controller.=20
> >>>=20
> >>> Signed-off-by: Tony Li <tony.li@freescale.com>=20
> >>=20
> >> Tony, have you looked at the 85xx/86xx PCIe MSI mechanism?=20
> >> The 2nd level PIC handling seems like its pretty similar=20
> >> between IPIC and MPIC. Would like to see if we could somehow=20
> >> make the code common for to handle MSIs from both?=20
> >>=20
> >> - k=20
> >>
>=20
next prev parent reply other threads:[~2007-12-14 9:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 10:39 [PATCH 2/2] powerpc: Add IPIC MSI support Li Li
2007-12-04 10:57 ` Li Yang
2007-12-04 11:59 ` Michael Ellerman
2007-12-14 5:44 ` Kumar Gala
2007-12-14 8:47 ` Li Tony
2007-12-14 8:52 ` Kumar Gala
2007-12-14 9:13 ` Li Li [this message]
2007-12-14 9:39 ` Jin Zhengxiong
2007-12-14 9:40 ` Michael Ellerman
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=1197623627.5016.1.camel@Guyver \
--to=r64360@freescale.com \
--cc=Jason.Jin@freescale.com \
--cc=Kim.Phillips@freescale.com \
--cc=Tony.Li@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.