linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Grant Likely" <grant.likely@secretlab.ca>,
	"Josh Boyer" <jwboyer@linux.vnet.ibm.com>,
	linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Device tree bindings for Xilinx devices
Date: Wed, 10 Oct 2007 23:27:14 -0600	[thread overview]
Message-ID: <fa686aa40710102227j474a4025p6f3aa7118adf03db@mail.gmail.com> (raw)
In-Reply-To: <20071011050850.GI14873@localhost.localdomain>

On 10/10/07, David Gibson <dwg@au1.ibm.com> wrote:
> > My main concern is that I don't like the implicit numbering that
> > occurs simply based on the order of devices in the device tree.  If
> > the probe algorithm ever changes to parse in reverse order or
> > something reorders the tree, then the device numbers also change.  :-(
>
> Way of the future, apparently, everything's supposed to use udev to
> give things logical names.  No, I'm not thrilled at the prospect
> either.

...

So in the OF aliases approach, would udev need to read the aliases
node when assigning names to devices?

>
> > I'd rather be explicit.  In fact I've already been bitten by this
> > where the mpc5200 has 6 PSC, each of which can be configured as a
> > serial port.  However, I've got access to 3 different boards; each of
> > which has the logical port numbers 100% unrelated to the 'cell'
> > number.
>
> In any case, this can't really belong in a *device* binding.  Because
> the numbering has to cross devices of the same basic type, but
> different implementations.  Where "basic type" is based on how device
> names are allocated, and is thus inherently Linux specific.

Okay, that makes sense.

> > > Segher's suggestion of using OF-style aliases for this is a fairly
> > > good one, actually.  I just need to get to implementing it...
> >
> > /me needs to look up what that look like and how I would use it.  My
> > knowledge of OF is sadly lacking.
>
> Short version by example:
> / {
>         /* ... */
>         aliases {
>                 hd = "/pci@f0000000/sata@f4000000/....";
>                 enet0 = "/soc/ethernet@c000";
>                 enet1 = "/soc/ethernet@d000";
>                 enet2 = "/pci@f0000000/isa/ethernet@i480"
>                 ttya = "/soc/serial@e000";
>                 ttyb = "/pci/isa/serail@3f8";
>         }
> }

Ah, my plan worked...  I got you to teach me about OF aliases and I
have to do any work myself.  :-)

Hmm, yes that would provide the information nicely.  As long as the
data is in the tree, I'm pretty happy.

Cheers,
g.

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


-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195

  reply	other threads:[~2007-10-11  5:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08  7:53 [PATCH] Device tree bindings for Xilinx devices Grant Likely
2007-10-10 16:39 ` Grant Likely
2007-10-10 20:38 ` Josh Boyer
2007-10-11  1:38   ` David Gibson
2007-10-11  2:25     ` Grant Likely
2007-10-11  4:06       ` David Gibson
2007-10-11  4:18         ` Grant Likely
2007-10-11  4:24           ` David Gibson
2007-10-11  4:58             ` Grant Likely
2007-10-11  5:08               ` David Gibson
2007-10-11  5:27                 ` Grant Likely [this message]
2007-10-12  3:14                   ` 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=fa686aa40710102227j474a4025p6f3aa7118adf03db@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=jwboyer@linux.vnet.ibm.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).