From: David Gibson <david@gibson.dropbear.id.au>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Sean MacLennan <smaclennan@pikatech.com>
Subject: Re: How complete should the DTS be?
Date: Thu, 10 Jan 2008 14:13:31 +1100 [thread overview]
Message-ID: <20080110031331.GF17816@localhost.localdomain> (raw)
In-Reply-To: <86AA8535-E2CF-4891-900B-340049A5CA19@kernel.crashing.org>
On Tue, Jan 08, 2008 at 12:04:36AM -0600, Kumar Gala wrote:
>
> On Jan 7, 2008, at 8:07 PM, Sean MacLennan wrote:
>
> > Just a general question about DTS "completeness". Like all 440EP
> > processors, the taco has two i2c buses. However, only one bus has
> > anything connected to it.
> >
> > Should I show both bus entries in the DTS, or only the one that is
> > used?
> > I have generally only been showing the devices that are present. i.e.
> > Only one emac, only one serial port.
> >
> > Is there a convention for this?
>
> The .dts should reflect the HW as its used. On some reference boards
> we might put out more info because of the various configs these types
> of boards can be setup in. However if something has a static config
> just describe that. So in your example of two i2c buses with only one
> connected, just describe the one that is used.
Hrm... I'd say this is not something which has a firm convention yet.
It's going to become more of an issue once we get a macros system for
dtc, so the "440EP" macro would have all the devices, even if some are
not connected on a given board.
I'm contemplating suggesting that we adopt the "status" property from
IEEE1275 to cover this.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
next prev parent reply other threads:[~2008-01-10 3:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 2:07 How complete should the DTS be? Sean MacLennan
2008-01-08 6:04 ` Kumar Gala
2008-01-10 3:13 ` David Gibson [this message]
2008-01-10 5:53 ` Sean MacLennan
2008-01-10 6:02 ` David Gibson
2008-01-10 6:50 ` Benjamin Herrenschmidt
2008-01-10 13:58 ` Josh Boyer
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=20080110031331.GF17816@localhost.localdomain \
--to=david@gibson.dropbear.id.au \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=smaclennan@pikatech.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).