From: David Gibson <dwg@au1.ibm.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Device tree bindings for Xilinx devices
Date: Thu, 11 Oct 2007 14:24:41 +1000 [thread overview]
Message-ID: <20071011042441.GG14873@localhost.localdomain> (raw)
In-Reply-To: <fa686aa40710102118p3e62d06eqff8db252772eb58c@mail.gmail.com>
On Wed, Oct 10, 2007 at 10:18:50PM -0600, Grant Likely wrote:
> On 10/10/07, David Gibson <dwg@au1.ibm.com> wrote:
> > On Wed, Oct 10, 2007 at 08:25:36PM -0600, Grant Likely wrote:
> > > On 10/10/07, David Gibson <dwg@au1.ibm.com> wrote:
> > > > We've used 'cell-index' for similar purposes on other 4xx.
> > >
> > > Unfortunately, 'cell' has been used in the sense of a logic cell in an
> > > SoC. In the case of the SystemACE, it is an external chip.
> > >
> > > What about "device-number"?
> >
> > Ok, I misunderstood. If it's not on chip, what significance does this
> > serial number have? Where would a driver need it?
>
> If there were 2 systemace devices on board; one attached to a CF slot
> labeled "1" and the other to one labeled "2". :-) Same problem as
> lining up serial device files to physical port numbers.
>
> The driver doesn't technically need it, but the information does need
> to flow through to the creation of logically numbered device files.
Ah. Then, I'm afraid it doesn't belong in the core binding.
Preferably, you should just figure out something without help of this
property - plenty of other things have to figure out device names
without assistance like this.
If you really must you could do this in analogy with the
"linux,network-index" property - but this would be, as that is, an
ugly hack, and should be recognized as such.
Segher's suggestion of using OF-style aliases for this is a fairly
good one, actually. I just need to get to implementing it...
--
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:[~2007-10-11 4:25 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 [this message]
2007-10-11 4:58 ` Grant Likely
2007-10-11 5:08 ` David Gibson
2007-10-11 5:27 ` Grant Likely
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=20071011042441.GG14873@localhost.localdomain \
--to=dwg@au1.ibm.com \
--cc=grant.likely@secretlab.ca \
--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).