Porting RapidIO from ppc arch to powerpc arch in support ofMPC8641D
Zhang Wei-r63237
Wei.Zhang at freescale.com
Thu May 24 17:31:39 EST 2007
> > > interrupts = <30 1 31 1 32 1 35 1 36 1
> 37 1 38 1>;
> > > > };
> > > >
> > > Do you really use all of this interrupts? In my test,
> three <32 2 35 2
> > > 36 2> are okay, and the sense is 2.
> >
> > I think we need to list all the interrupts possible from
> RIO, not just the
> > ones the driver happens to use.
> Sorry about the senses, again I just threw that in the email as a
> strawman to kick off discussion (which now seems moot as Wei has the
> patches (yippee)). The second set of interrupts 37 and 38 are for the
> second message unit which I want to use (see above). 30 is for
> port-write/error which I will be using to get interrupts from my
> switches for topology changes. 31 is the out doorbell done which the
> driver doesn't use cos of the synchronous nature of the out doorbell I
> suppose.
About this interrupts, I suggest to put the BELL, Tx, Rx to the front of
others. These three is already be used in ppc rio codes.
For example:
/* bell_irq tx_irq rx_irq */
interrupts = <32 2 35 2 36 2>;
Thanks!
Wei.
More information about the Linuxppc-dev
mailing list