All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org,
	David DeBonis <ddeboni-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
	Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>,
	michal.simek-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org,
	John Linn <linnj-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
	John Williams
	<john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org>
Subject: Re: Device tree BSP
Date: Mon, 06 Jul 2009 08:10:58 +1000	[thread overview]
Message-ID: <1246831858.22625.4.camel@pasglop> (raw)
In-Reply-To: <fa686aa40907051453of20e849gab47e901ced28501-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Sun, 2009-07-05 at 15:53 -0600, Grant Likely wrote:
> This is not a question that I've got an answer to, but
> I've been thinking about defining a "machine" node, or something
> similar that can be a parent of such non-addressable devices.  I'm
> hoping Mitch, Ben, DavidG, Scott, or some other OF active folks will
> jump in here and give their opinion before I go and define something
> braindead.  I was thinking something like this, where the root node
> would be the parent of this machine node:

Well, device nodes can perfectly represent non addressable devices...
One way is to have no "reg" property but that sucks as you get no unit
address neither which can cause problems when you have multiple of them.

So hosting them under some kind of node that would break that address
translatability (have no "ranges" property) makes some amount of sense
though I don't necessarily like the term "machine".

But if no "reg" is good for you, then stick them in the soc node with
distinct names.

Also, why "virtual," in your compatible property for the SPI node ? It's
not really virtual... 

Cheers,
Ben.

  parent reply	other threads:[~2009-07-05 22:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4A49F472.3030902@petalogix.com>
2009-07-04 18:15 ` Device tree BSP Stephen Neuendorffer
     [not found]   ` <20090704181837.4DC219B0051-AP5P7IoXhpo/OHOHf44ZtvYhGscHeamf@public.gmane.org>
2009-07-05  9:18     ` John Williams
2009-07-05 20:43       ` Stephen Neuendorffer
     [not found]         ` <20090705204647.1BBCAB2004B-UG8A/UOmamfGqIK/7oNHF6QXxVRGGlT3@public.gmane.org>
2009-07-05 21:53           ` Grant Likely
     [not found]             ` <fa686aa40907051453of20e849gab47e901ced28501-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-07-05 22:10               ` Benjamin Herrenschmidt [this message]
2009-07-05 23:08                 ` Grant Likely
     [not found] ` <20090704181837.6224D13E8056@mail113-va3.bigfish.com>
     [not found]   ` <20090704181837.6224D13E8056-4w96H/B/PjLzgBzxlff1BqQXxVRGGlT3@public.gmane.org>
2009-07-04 18:32     ` Michal Simek

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=1246831858.22625.4.camel@pasglop \
    --to=benh-xvmvhmargas8u2djnn8i7kb+6bgklq7r@public.gmane.org \
    --cc=ddeboni-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
    --cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
    --cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
    --cc=john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org \
    --cc=linnj-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
    --cc=michal.simek-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org \
    --cc=scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.