Devicetree
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: David VomLehn <dvomlehn-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
Cc: Mailing-ZEW99E7oL/EiWxQNNj96ibh/4TqKg8J2XqFh9Ls21Oc@public.gmane.org,
	devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
	Tree-ZEW99E7oL/EiWxQNNj96ibh/4TqKg8J2XqFh9Ls21Oc@public.gmane.org,
	List-ZEW99E7oL/EiWxQNNj96ibh/4TqKg8J2XqFh9Ls21Oc@public.gmane.org,
	Device-ZEW99E7oL/EiWxQNNj96ibh/4TqKg8J2XqFh9Ls21Oc@public.gmane.org
Subject: Re: Wrapping proprietary nodes
Date: Tue, 26 Oct 2010 12:25:14 +0100	[thread overview]
Message-ID: <20101026112514.GC24714@angua.secretlab.ca> (raw)
In-Reply-To: <20101022214454.GB24896-ZEW99E7oL/EiWxQNNj96ibh/4TqKg8J2XqFh9Ls21Oc@public.gmane.org>

On Fri, Oct 22, 2010 at 02:44:54PM -0700, David VomLehn wrote:
> I expect my device tree will have some proprietary, one-off devices in
> it. Is it better to wrap these all up in one node:
> 
> 	cisco {
> 		device1 {
> 			...
> 		};
> 		device2 {
> 			...
> 		};
> 	};
> 
> Or should they be specified one node at a time:
> 
> 	cisco-device1 {
> 		...
> 	};
> 	cisco-device2 {
> 		...
> 	};
> 
> My inclination is for the former, but I'd prefer to follow existing usage,
> if any.

Neither.  The layout should reflect the actual hardware layout, and
the devices should follow the Generic Names recommended practice[1][2].

[1] http://playground.sun.com/1275/practice/gnames/gnamv14a.html
[2] http://www.power.org/resources/downloads/Power_ePAPR_APPROVED_v1.0.pdf
	section 2.2.2

The correct way to differentiate between devices (regardless of
whether or not the driver is proprietary, or if it is a custom device
for the system) is to use the 'compatible' property.  Therefore your
tree might look something like this:

	input@<address> {
		compatible = "cisco,<part/device>";
		...
	};
	dma-controller@<address> {
		compatible = "cisco,<part/device>";
		...
	};

g.


> -- 
> David VL
> _______________________________________________
> devicetree-discuss mailing list
> devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
> https://lists.ozlabs.org/listinfo/devicetree-discuss

      parent reply	other threads:[~2010-10-26 11:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22 21:44 Wrapping proprietary nodes David VomLehn
     [not found] ` <20101022214454.GB24896-ZEW99E7oL/EiWxQNNj96ibh/4TqKg8J2XqFh9Ls21Oc@public.gmane.org>
2010-10-24  7:01   ` David Gibson
2010-10-25 18:32   ` Yoder Stuart-B08248
     [not found]     ` <9696D7A991D0824DBA8DFAC74A9C5FA306911999-ofAVchDyotYzzZk0BCvKg5jmvxFtTJ+o0e7PPNI6Mm0@public.gmane.org>
2010-10-25 19:15       ` Segher Boessenkool
2010-10-25 20:40       ` David VomLehn
     [not found]         ` <20101025204054.GA1594-ZEW99E7oL/EiWxQNNj96ibh/4TqKg8J2XqFh9Ls21Oc@public.gmane.org>
2010-10-25 21:15           ` Yoder Stuart-B08248
2010-10-26 11:25   ` Grant Likely [this message]

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=20101026112514.GC24714@angua.secretlab.ca \
    --to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
    --cc=Device-ZEW99E7oL/EiWxQNNj96ibh/4TqKg8J2XqFh9Ls21Oc@public.gmane.org \
    --cc=List-ZEW99E7oL/EiWxQNNj96ibh/4TqKg8J2XqFh9Ls21Oc@public.gmane.org \
    --cc=Mailing-ZEW99E7oL/EiWxQNNj96ibh/4TqKg8J2XqFh9Ls21Oc@public.gmane.org \
    --cc=Tree-ZEW99E7oL/EiWxQNNj96ibh/4TqKg8J2XqFh9Ls21Oc@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=dvomlehn-FYB4Gu1CFyUAvxtiuMwx3w@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox