From: "Grant Likely" <grant.likely@secretlab.ca>
To: "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 22:58:25 -0600 [thread overview]
Message-ID: <fa686aa40710102158r5d488d3kae3d02177625da1e@mail.gmail.com> (raw)
In-Reply-To: <20071011042441.GG14873@localhost.localdomain>
On 10/10/07, David Gibson <dwg@au1.ibm.com> wrote:
> 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.
I'm not too stuck on the method used, but I do think it is appropriate
to encode this kind of data in the device tree in some form...
However, for this particular device I'm probably just borrowing
trouble. I'll drop the property.
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. :-(
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.
> 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...
/me needs to look up what that look like and how I would use it. My
knowledge of OF is sadly lacking.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-10-11 4:58 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 [this message]
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=fa686aa40710102158r5d488d3kae3d02177625da1e@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).