linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Matt Sealey <matt@genesi-usa.com>
Cc: linuxppc-dev@ozlabs.org, Anatolij Gustschin <agust@denx.de>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [RESEND][POWERPC] mpc5200: Amalgamated dts fixes and updates
Date: Thu, 27 Mar 2008 10:28:11 +1100	[thread overview]
Message-ID: <20080326232811.GA8005@localhost.localdomain> (raw)
In-Reply-To: <47EAD4DA.5050907@genesi-usa.com>

On Wed, Mar 26, 2008 at 10:57:30PM +0000, Matt Sealey wrote:
> David Gibson wrote:
>> On Wed, Mar 26, 2008 at 03:16:47PM -0600, Grant Likely wrote:
>>> On Wed, Mar 26, 2008 at 3:02 PM, Matt Sealey <matt@genesi-usa.com> wrote:
>>>> Bartlomiej Sieka wrote:
>>>>  > +
>>>>  > +                     phy0:ethernet-phy@0 {
>>>>  > +                             device_type = "ethernet-phy";@0"
>>>>  > +                             reg = <0>;
>>>>  > +                     };
>>>>
>>>>  What's the parsing of this pan out to? What does it mean?
>>>>
>>>>  Having colons in device names is totally contrary to OF device naming
>>>>  spec. Does the part after the colon have a special meaning to the DTC?
>>> "phy0:" is a label used by dtc.
>>> "ethernet-phy@0" is the node name.
>> I would suggest a space after the colon though, to make this clearer.
>> That's the style I've been using in all my dts files.
>
> I would suggest taking a hint from C structures...
>
> ethernet-phy@0 {
> 	name = "ethernet-phy";
> 	reg = <0>;
> 	foo = bar;
> } phy0;
>
> I mean, this is really intuitive, we all do this every day...

That's a terrible analogy though.  The OF name is in no way like a
structure's type, which is what would go there.  Plus it separates the
label from the top of the node which will make it harder to read.

The label syntax is already based on C labels, and can be used more
places than just nodes.  Putting a space should make it rather
clearer, and is also closer to normal C style (how many people would
write
	out:return(err);

-- 
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

  reply	other threads:[~2008-03-26 23:28 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20 14:18 Oops with TQM5200 on TQM5200 Wolfgang Grandegger
2008-03-20 14:41 ` Grant Likely
2008-03-20 15:24 ` Anatolij Gustschin
2008-03-20 16:17   ` Bartlomiej Sieka
2008-03-20 21:27     ` Grant Likely
2008-03-22 10:49       ` Anatolij Gustschin
2008-03-22 14:39         ` Grant Likely
2008-03-20 16:29   ` Wolfgang Grandegger
2008-03-20 23:50   ` Grant Likely
2008-03-21  0:07     ` Bartlomiej Sieka
2008-03-21  0:20       ` Grant Likely
2008-03-21 23:56         ` [POWERPC] mpc52xx: Amalgamated dts fixes and updates Bartlomiej Sieka
2008-03-22  0:12           ` David Gibson
2008-03-22  3:47             ` Grant Likely
2008-03-22  0:41           ` Anatolij Gustschin
2008-03-22  3:14           ` Grant Likely
2008-03-26 19:45             ` [RESEND][POWERPC] mpc5200: " Bartlomiej Sieka
2008-03-26 20:35               ` Grant Likely
2008-03-26 20:48                 ` Wolfgang Grandegger
2008-03-26 21:32                   ` Bartlomiej Sieka
2008-03-26 21:18                 ` [RESEND2][POWERPC] " Bartlomiej Sieka
2008-03-26 21:02               ` [RESEND][POWERPC] " Matt Sealey
2008-03-26 21:16                 ` Grant Likely
2008-03-26 22:51                   ` David Gibson
2008-03-26 22:57                     ` Matt Sealey
2008-03-26 23:28                       ` David Gibson [this message]
2008-03-24 16:59           ` [POWERPC] mpc52xx: " Wolfgang Grandegger
2008-03-21  6:30       ` Oops with TQM5200 on TQM5200 Wolfgang Grandegger
2008-03-21 19:02         ` Grant Likely
2008-03-24  6:47         ` Paul Mackerras
2008-03-25  9:54           ` Wolfgang Grandegger

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=20080326232811.GA8005@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=agust@denx.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=matt@genesi-usa.com \
    --cc=paulus@samba.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).