From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Yoder Stuart-B08248" <stuart.yoder@freescale.com>
Cc: linuxppc-dev Development <linuxppc-dev@ozlabs.org>,
Sven Luther <sven@genesi-usa.com>
Subject: Re: Discussion on SOC device tree bindings
Date: Fri, 19 Jan 2007 09:38:36 -0700 [thread overview]
Message-ID: <528646bc0701190838w106d6407h9516ccc37349111a@mail.gmail.com> (raw)
In-Reply-To: <9696D7A991D0824DBA8DFAC74A9C5FA3023612F8@az33exm25.fsl.freescale.net>
On 1/19/07, Yoder Stuart-B08248 <stuart.yoder@freescale.com> wrote:
>
> Back in Grant's original summary of the problem he wrote:
> >
> > 5. The contentious issue is which direction those links should be
> > constructed. Does the device node describe where to find it's SoC
> > parent node and what the device index is? Or does the SoC node
> > describe which device nodes it provides shared register service for?
>
> How about linking in _both_ directions?
I think that's a bad precedence. Either representation can be
generated from the other. Linking it in both directions means
duplicate information with no real benefit.
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-01-19 16:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <528646bc0701131555n3249b503i3b6e8c37db41dd52@mail.gmail.com>
2007-01-14 22:29 ` Discussion on SOC device tree bindings Grant Likely
2007-01-15 11:05 ` Sascha Hauer
2007-01-15 13:48 ` Grant Likely
2007-01-15 15:42 ` Segher Boessenkool
2007-01-16 8:25 ` Sascha Hauer
[not found] ` <45AA098C.70101@246tNt.com>
[not found] ` <6189b01379f62aa4516484872f4ef86f@kernel.crashing.org>
[not found] ` <1168810790.4803.11.camel@localhost.localdomain>
[not found] ` <ccc8fbc935d8f8d3e30870d43959f6c7@kernel.crashing.org>
[not found] ` <1168817449.4803.28.camel@localhost.localdomain>
[not found] ` <ef64a4198a02929a00c28abb5f0934b5@kernel.crashing.org>
[not found] ` <1168818533.4803.37.camel@localhost.localdomain>
[not found] ` <a1af25147ea7308c394d243511b96f69@kernel.crashing.org>
[not found] ` <45ABA20E.30008@genesi-usa.com>
2007-01-15 17:06 ` Grant Likely
2007-01-15 18:31 ` Segher Boessenkool
2007-01-16 6:25 ` Benjamin Herrenschmidt
2007-01-16 9:07 ` Segher Boessenkool
[not found] ` <1168928567.4803.55.camel@localhost.localdomain>
2007-01-17 8:40 ` Grant Likely
2007-01-19 10:58 ` Segher Boessenkool
2007-01-19 16:11 ` Yoder Stuart-B08248
2007-01-19 16:38 ` Grant Likely [this message]
2007-01-19 16:50 ` Segher Boessenkool
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=528646bc0701190838w106d6407h9516ccc37349111a@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=stuart.yoder@freescale.com \
--cc=sven@genesi-usa.com \
/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).