From: Benjamin Herrenschmidt <benh@au1.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Christian Rund <Christian.Rund@de.ibm.com>,
Hartmut Penner <HPENNER@de.ibm.com>,
Murali N Iyer <mniyer@us.ibm.com>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: EMAC OF binding....
Date: Wed, 10 Jan 2007 09:04:48 +1100 [thread overview]
Message-ID: <1168380289.22458.313.camel@localhost.localdomain> (raw)
In-Reply-To: <e4d627ebdd8e678a0441bc0649714de8@kernel.crashing.org>
On Tue, 2007-01-09 at 22:57 +0100, Segher Boessenkool wrote:
> > Well, we use that method for most things,for example, the emac has
> > phandles to the zmii/rgmii/etc... for that specific case however, I
> > still prefer a cell index.
>
> How about you put both in the device tree, and the kernel
> can use whatever it wants -- best of both worlds :-)
I don't see the need of having some weird "soc" node that doesn't quite
mean anything (especially on axon) that has phandles to every sub device
in there :-)
I really don't see the interest in your approach but I may have missed
something.
On those ASICs, every device almost needs to know what is it's "cell
index" because of little details here or there. I really see that as an
attribute of the device and thus should be a property of the node.
Ben.
next prev parent reply other threads:[~2007-01-09 22:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF7EF2F643.75F7008B-ON8625725D.00157658-8625725D.00167CB4@au1.ibm.com>
2007-01-08 6:09 ` EMAC OF binding Benjamin Herrenschmidt
2007-01-08 6:38 ` Segher Boessenkool
2007-01-08 20:32 ` Benjamin Herrenschmidt
2007-01-08 22:12 ` David Gibson
2007-01-08 23:34 ` Segher Boessenkool
2007-01-08 22:40 ` Segher Boessenkool
2007-01-08 22:47 ` Benjamin Herrenschmidt
2007-01-08 23:27 ` Segher Boessenkool
2007-01-09 0:30 ` Benjamin Herrenschmidt
2007-01-09 16:08 ` Segher Boessenkool
2007-01-09 21:45 ` Benjamin Herrenschmidt
2007-01-09 21:57 ` Segher Boessenkool
2007-01-09 22:04 ` Benjamin Herrenschmidt [this message]
2007-01-09 22:17 ` Segher Boessenkool
2007-01-09 22:41 ` David Gibson
2007-01-09 22:42 ` Benjamin Herrenschmidt
2007-01-09 23:05 ` Segher Boessenkool
2007-01-30 0:25 ` Benjamin Herrenschmidt
2007-01-30 0:45 ` Kumar Gala
2007-01-30 0:54 ` David Gibson
2007-01-30 1:50 ` Benjamin Herrenschmidt
2007-01-30 2:49 ` Benjamin Herrenschmidt
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=1168380289.22458.313.camel@localhost.localdomain \
--to=benh@au1.ibm.com \
--cc=Christian.Rund@de.ibm.com \
--cc=HPENNER@de.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mniyer@us.ibm.com \
--cc=segher@kernel.crashing.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).