linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Scott Wood <scottwood@freescale.com>,
	linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: New fsl device bindings file
Date: Thu, 3 Jul 2008 22:26:01 -0600	[thread overview]
Message-ID: <20080704042601.GI12945@secretlab.ca> (raw)
In-Reply-To: <BE229B94-773D-4FA8-AFD0-E46F5887F8D3@kernel.crashing.org>

On Thu, Jul 03, 2008 at 01:38:17PM -0500, Kumar Gala wrote:
>
> On Jul 3, 2008, at 1:34 PM, Grant Likely wrote:
>
>> On Thu, Jul 3, 2008 at 12:28 PM, Scott Wood <scottwood@freescale.com> 
>> wrote:
>>> Documentation/powerpc/device-tree/fsl/cpm.txt
>>> Documentation/powerpc/device-tree/fsl/cpm/uart.txt
>>> Documentation/powerpc/device-tree/fsl/tsec.txt
>>> Documentation/powerpc/device-tree/interrupts.txt
>>> Documentation/powerpc/device-tree/dtb.txt
>>
>> May I suggest moving it to Documentation/of-bindings/ instead?  Some
>> of these bindings (granted, not the fsl ones) will be used by
>> non-powerpc platforms (sparc, microblaze).
>
> I think the powerpc bindings should still be under Docs/powerpc/of- 
> bindings/
>
> It makes it cleaner in that each arch/sub-arch maintainer can maintain  
> Docs/<arch>/of-bindings and we can all vet changes to Docs/of-bindings

Personally, I think it would still be better to keep everything in one
place, even if large parts of it are arch specific.  I think it would
encourage people to look across architecture boundaries when looking for
examples of how to document device tree bindings.  It would also
discourage accidental duplication for parts that end up being used in
more than one architectures (ie. spi and i2c devices).  Not everyone is
going to be well versed on the rules of what bindings should be arch
specific and what should go in the common dir.  It will make everyone's
life easier if there is only one place to look.

(oh, and I think the subdirectories by manufacturer is a good layout).

g.

  reply	other threads:[~2008-07-04  4:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-03 18:20 New fsl device bindings file Kumar Gala
2008-07-03 18:28 ` Scott Wood
2008-07-03 18:34   ` Grant Likely
2008-07-03 18:38     ` Kumar Gala
2008-07-04  4:26       ` Grant Likely [this message]
2008-07-05  5:24     ` Olof Johansson
2008-07-07  1:39       ` David Gibson
2008-07-07  1:45         ` Olof Johansson
2008-07-07 15:28           ` Kumar Gala
2008-07-03 18:36   ` Kumar Gala
2008-07-05 11:34   ` Jochen Friedrich
2008-07-03 18:53 ` Anton Vorontsov
2008-07-03 23:36   ` Paul Mackerras
2008-07-04 13:33   ` Matt Sealey
2008-07-04 23:12     ` Segher Boessenkool
2008-07-05  1:26       ` David Gibson
2008-07-05  6:53         ` Grant Likely
2008-07-04 22:59   ` Segher Boessenkool
2008-07-04 23:14 ` 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=20080704042601.GI12945@secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.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).