From: Kumar Gala <galak@kernel.crashing.org>
To: Zhang Wei-r63237 <Wei.Zhang@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: RE: Porting RapidIO from ppc arch to powerpc arch in support of MPC8641D
Date: Wed, 23 May 2007 09:21:48 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0705230916170.535@localhost.localdomain> (raw)
In-Reply-To: <46B96294322F7D458F9648B60E15112C234AE6@zch01exm26.fsl.freescale.net>
On Wed, 23 May 2007, Zhang Wei-r63237 wrote:
> > So I'm taking the boot/dts/mpc8641_hpcn.dts and producing a new
> > mpc8641D_umem.dts with the following addition to the soc.
> >
> > srio@c0000 {
> > device_type = "srio";
> > compatible = "86xx,85xx";
We really need to think about this, is their really any difference between
srio and prio from a software view point?
> > reg = <c0000 20000>;
> > law = <400000000 e00000000>;
>
> Please use range = <0 address_start size>
The law should really be removed.
>
> > dbells = <0 ffff>;
> > mboxs = <0 4>;
>
> The dbells and mboxs can be removed. The default setting in rio is okay.
this could possibly be useful.
>
> > interrupt-parent = <&mpic>;
> > 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.
- k
next prev parent reply other threads:[~2007-05-23 14:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 19:38 Porting RapidIO from ppc arch to powerpc arch in support of MPC8641D Phil Terry
2007-05-22 20:08 ` Segher Boessenkool
2007-05-22 20:09 ` Timur Tabi
2007-05-22 23:05 ` Arnd Bergmann
2007-05-24 6:48 ` Porting RapidIO from ppc arch to powerpc arch in support ofMPC8641D Zhang Wei-r63237
2007-05-24 9:19 ` Arnd Bergmann
2007-05-24 9:44 ` Zhang Wei-r63237
2007-05-24 11:27 ` Arnd Bergmann
2007-05-23 13:26 ` Porting RapidIO from ppc arch to powerpc arch in support of MPC8641D Zhang Wei-r63237
2007-05-23 13:32 ` Mark A. Greer
2007-05-23 14:03 ` Zhang Wei-r63237
2007-05-23 15:42 ` Phil Terry
2007-05-23 15:53 ` Mark A. Greer
2007-05-23 15:54 ` Phil Terry
2007-05-23 14:21 ` Kumar Gala [this message]
2007-05-23 15:37 ` Phil Terry
2007-05-23 16:05 ` Segher Boessenkool
2007-05-23 16:20 ` Phil Terry
2007-05-23 16:20 ` Kumar Gala
2007-05-23 16:43 ` Phil Terry
2007-05-23 23:17 ` Segher Boessenkool
2007-05-23 23:05 ` Segher Boessenkool
2007-05-24 7:31 ` Porting RapidIO from ppc arch to powerpc arch in support ofMPC8641D Zhang Wei-r63237
2007-05-23 16:00 ` Porting RapidIO from ppc arch to powerpc arch in support of MPC8641D Segher Boessenkool
2007-05-23 16:13 ` Phil Terry
2007-05-24 0:52 ` David Gibson
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.0705230916170.535@localhost.localdomain \
--to=galak@kernel.crashing.org \
--cc=Wei.Zhang@freescale.com \
--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).