From: David Gibson <david@gibson.dropbear.id.au>
To: Heiko Schocher <hs@denx.de>
Cc: Scott Wood <scottwood@freescale.com>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v4] 83xx: add support for the kmeter1 board.
Date: Mon, 15 Jun 2009 12:42:52 +1000 [thread overview]
Message-ID: <20090615024252.GC25444@yookeroo.seuss> (raw)
In-Reply-To: <4A31E74E.6090505@denx.de>
On Fri, Jun 12, 2009 at 07:27:42AM +0200, Heiko Schocher wrote:
> Hello David,
>
> David Gibson wrote:
> > On Thu, Jun 11, 2009 at 08:10:41PM +0200, Heiko Schocher wrote:
> >> The following series implements basic board support for
> >> the kmeter1 board from keymile, based on a MPC8360.
> >
> > [snip]
> >> + par_io@1400 {
> >> + reg = <0x1400 0x100>;
> >> + device_type = "par_io";
> >
> > This should have a compatible value instead of a device_type value.
>
> compatible = "fsl,mpc8360-par_io"; ?
Sounds reasonable, if there isn't an existing precedent to follow.
> > [snip]
> >
> >> + num-ports = <7>;
> >> +
> >> + pio_ucc1: ucc_pin@00 {
> >
> > Since these nodes have addresses, they should also have reg
> > properties. And the parent should have #address-cells and
> > #size-cells.
>
> added "#address-cells" and "#size-cells", but couldn;t find what
> I should write in a "reg" entry ... I think something like that:
>
> reg = <0x00 0x01>;
If you just want a plain index number, which is what it seems you have
here, then you'll want #address-cells = 1, #size-cells = 0 and reg
will then have one cell (i.e. 1 u32) with the index number
so subnode@0 {
reg = <0>;
}
subnode@1 {
reg = <1>;
}
Note also that it's usual for the unit addresses (that's the bits
after the @ sign) to be formatted without leading zeroes.
>
> ?
>
> > [snip]
> >> + qe@100000 {
> >> + #address-cells = <1>;
> >> + #size-cells = <1>;
> >> + device_type = "qe";
> >
> > This device_type should not be here.
>
> deleted.
Ok.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2009-06-15 2:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 6:09 [PATCH] 83xx: add support for the kmeter1 board Heiko Schocher
2009-04-23 14:25 ` Kumar Gala
2009-04-23 14:50 ` Heiko Schocher
2009-04-27 5:38 ` Heiko Schocher
2009-04-27 18:05 ` Scott Wood
2009-04-28 4:42 ` Heiko Schocher
2009-04-28 16:35 ` Scott Wood
2009-04-29 4:48 ` [PATCH v2] " Heiko Schocher
2009-06-11 2:43 ` Kumar Gala
2009-06-11 6:03 ` Heiko Schocher
2009-06-11 6:16 ` [PATCH v3] " Heiko Schocher
2009-06-11 14:10 ` Kumar Gala
2009-06-11 18:08 ` Heiko Schocher
2009-06-11 18:10 ` [PATCH v4] " Heiko Schocher
2009-06-12 1:13 ` David Gibson
2009-06-12 5:27 ` Heiko Schocher
2009-06-15 2:42 ` David Gibson [this message]
2009-06-15 7:38 ` [PATCH v5] " Heiko Schocher
2009-06-16 3:16 ` Kumar Gala
2009-05-07 17:49 ` [PATCH] " Varlese, Christopher
2009-05-08 5:44 ` Heiko Schocher
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=20090615024252.GC25444@yookeroo.seuss \
--to=david@gibson.dropbear.id.au \
--cc=hs@denx.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.com \
/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).