From: Wade Farnsworth <wfarnsworth@mvista.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 2/8] Add uli1575 pci-bridge sector to MPC8641HPCN dts file.
Date: Fri, 01 Jun 2007 14:45:14 -0700 [thread overview]
Message-ID: <1180734314.5674.49.camel@rhino> (raw)
In-Reply-To: <dfc15991e31bfc09389461dc443acd7c@kernel.crashing.org>
On Fri, 2007-06-01 at 20:58 +0200, Segher Boessenkool wrote:
> > + ranges = <00000000 f8000000 00100000
> > + 80000000 80000000 20000000
> > + e2000000 e2000000 00100000
> > + a0000000 a0000000 20000000
> > + e3000000 e3000000 00100000>;
> > reg = <f8000000 00100000>; // CCSRBAR 1M
>
>
> "reg" included in "ranges"? Something is wrong here.
I think it's correct for soc nodes. At least, it appears that all of
the dts files with soc nodes do similar things (including this one even
without this patch).
>
> > + pci_bridge@0 {
>
> > + #size-cells = <2>;
> > + #address-cells = <3>;
> > + ranges = <02000000 0 80000000
> > + 02000000 0 80000000
> > + 0 20000000
> > + 01000000 0 00000000
> > + 01000000 0 00000000
> > + 0 00100000>;
> > +
> > + isa@1e {
> > + #size-cells = <1>;
> > + #address-cells = <2>;
> >
> > + ranges = <1 0 01000000 0 0
> > + 00001000>;
>
> You map the same range (4kB legacy I/O @ 0) for both
> bridges here.
There is a one-to-one mapping between the I/O spaces of "isa" and
"pci_bridge", so wouldn't it be reasonable that a similar range be used?
>
> > + i8042@60 {
> > + reg = <1 60 1 1 64 1>;
>
> And this address space is included in both of those.
Again, shouldn't the child's address space be in its parent's range?
>
> > + keyboard@0 {
> > + compatible = "pnpPNP,303";
> > + };
> > +
> > + mouse@1 {
> > + compatible = "pnpPNP,f03";
> > + };
>
> These need a "reg" property.
I'll add them.
>
> > + rtc@70 {
> > + compatible =
> > + "pnpPNP,b00";
> > + reg = <1 70 2>;
> > + };
> > +
> > + gpio@400 {
> > + reg = <1 400 80>;
> > + };
>
> Inclusive again.
See above.
>
> > + i8259: i8259@4d0 {
>
> Needs "reg". And 4d0 isn't the primary address
> I think?
Yes, this is a standard i8259 with additional registers at 0x20 and
0xa0. I'll fix the address and add the registers.
--Wade
next prev parent reply other threads:[~2007-06-01 21:45 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 17:48 [PATCH 2/8] Add uli1575 pci-bridge sector to MPC8641HPCN dts file Jon Loeliger
2007-06-01 18:58 ` Segher Boessenkool
2007-06-01 21:45 ` Wade Farnsworth [this message]
2007-06-02 8:22 ` Segher Boessenkool
2007-06-02 8:53 ` Gabriel Paubert
2007-06-02 9:01 ` Segher Boessenkool
2007-06-02 19:53 ` Gabriel Paubert
2007-06-02 20:23 ` Segher Boessenkool
2007-06-03 0:01 ` Benjamin Herrenschmidt
2007-06-03 7:41 ` Segher Boessenkool
2007-06-03 8:33 ` Gabriel Paubert
2007-06-03 8:57 ` Segher Boessenkool
2007-06-03 9:12 ` Benjamin Herrenschmidt
2007-06-03 10:02 ` Segher Boessenkool
2007-06-03 10:10 ` Gabriel Paubert
2007-06-03 11:42 ` Segher Boessenkool
2007-06-03 12:43 ` Gabriel Paubert
2007-06-03 14:42 ` Segher Boessenkool
2007-06-03 18:20 ` Gabriel Paubert
2007-06-03 18:56 ` Segher Boessenkool
2007-06-03 9:07 ` Benjamin Herrenschmidt
2007-06-03 9:59 ` Segher Boessenkool
2007-06-03 14:50 ` Jon Loeliger
2007-06-03 17:27 ` Segher Boessenkool
2007-06-04 20:27 ` Andy Fleming
2007-06-04 22:31 ` Randy Vinson
2007-06-05 19:16 ` Andy Fleming
2007-06-05 20:28 ` Randy Vinson
2007-06-06 7:09 ` Benjamin Herrenschmidt
2007-06-07 16:21 ` Andy Fleming
2007-06-07 16:53 ` Segher Boessenkool
2007-06-07 22:12 ` Benjamin Herrenschmidt
2007-06-08 8:29 ` Segher Boessenkool
2007-06-08 8:32 ` Benjamin Herrenschmidt
2007-06-05 6:05 ` Zang Roy-r61911
2007-06-02 23:52 ` Benjamin Herrenschmidt
2007-06-02 23:51 ` Benjamin Herrenschmidt
2007-06-03 8:59 ` Geert Uytterhoeven
2007-06-04 18:50 ` Jon Loeliger
2007-06-04 19:27 ` Segher Boessenkool
2007-06-01 23:28 ` Benjamin Herrenschmidt
2007-06-01 23:36 ` Jon Loeliger
2007-06-02 0:22 ` Benjamin Herrenschmidt
2007-06-02 8:28 ` Segher Boessenkool
2007-06-02 16:04 ` Jon Loeliger
2007-06-02 20:00 ` Segher Boessenkool
2007-06-02 23:16 ` Benjamin Herrenschmidt
2007-06-03 7:37 ` Segher Boessenkool
2007-06-04 0:16 ` Olof Johansson
2007-06-04 8:18 ` Segher Boessenkool
2007-06-02 8:25 ` Segher Boessenkool
2007-06-02 23:50 ` Benjamin Herrenschmidt
2007-06-03 0:13 ` Gabriel Paubert
2007-06-03 7:42 ` Segher Boessenkool
2007-06-03 7:53 ` Gabriel Paubert
2007-06-04 18:49 ` Jon Loeliger
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=1180734314.5674.49.camel@rhino \
--to=wfarnsworth@mvista.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=segher@kernel.crashing.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).