linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, Timur Tabi <timur@freescale.com>
Subject: Re: [PATCH 3/3] [POWERPC] Add docs for Freescale DMA & DMA channel device tree nodes
Date: Wed, 21 Nov 2007 11:35:40 -0600	[thread overview]
Message-ID: <20071121173540.GC4413@loki.buserror.net> (raw)
In-Reply-To: <E9CED991-4E10-44AE-A446-B6CB151FB9EE@kernel.crashing.org>

On Wed, Nov 21, 2007 at 09:33:05AM -0600, Kumar Gala wrote:
> On Nov 21, 2007, at 8:59 AM, Timur Tabi wrote:
> >> +  Example:
> >> +	dma@21000 {
> >
> > Shouldn't this be dma@21300?
> 
> its an example that has not basis is reality :)

But it should at least be internally consistent with this:

> >> +		reg = <21300 4>;

[snip]
> > The DMA controller and the DMA channels need a "device-id", so that  
> > they can be identified by number.  Some peripherals, like the SSI,  
> > can only use the controller and channel number.  This is what I have  
> > in my 8610 DTS:
> 
> Why not use reg for this?  I don't see any reason to add another  
> "unique id" when there is already one.

A cell-index property would be useful here for indexing into the summary
status register.

> 
> >                dma@21300 {
> >                        #address-cells = <1>;
> >                        #size-cells = <1>;
> >                        compatible = "fsl,mpc8610-dma", "fsl,mpc8540- 
> > dma";
> >        -->             device-id = <0>;

I don't see any justification for having such a property in the parent node,
though.

-Scott

  reply	other threads:[~2007-11-21 17:35 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-21  5:11 [PATCH 0/3] Device tree docs updates for FSL periphs Kumar Gala
2007-11-21  5:12 ` [PATCH 1/3] [POWERPC] Add docs for Freescale 83xx SATA device tree nodes Kumar Gala
2007-11-25 22:22   ` Arnd Bergmann
2007-11-26 15:41     ` Kumar Gala
2007-11-26 16:06       ` Arnd Bergmann
2007-12-03  2:37   ` Li Yang
2007-11-21  5:13 ` [PATCH 2/3] [POWERPC] Add docs for Freescale RapidIO device tree node Kumar Gala
2007-11-21 17:29   ` Scott Wood
2007-11-21 19:20     ` Kumar Gala
2007-11-21  5:14 ` [PATCH 3/3] [POWERPC] Add docs for Freescale DMA & DMA channel device tree nodes Kumar Gala
2007-11-21 14:59   ` Timur Tabi
2007-11-21 15:33     ` Kumar Gala
2007-11-21 17:35       ` Scott Wood [this message]
2007-11-21 19:21         ` Kumar Gala
2007-11-21 19:27           ` Scott Wood
2007-11-21 22:28             ` David Gibson
2007-11-22  0:51               ` Timur Tabi
2007-11-26 15:44                 ` Scott Wood
2007-11-22  0:49         ` Timur Tabi
2007-11-22  0:48       ` Timur Tabi
2007-11-21 17:33   ` Scott Wood
2007-11-21 19:19     ` Kumar Gala

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=20071121173540.GC4413@loki.buserror.net \
    --to=scottwood@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=timur@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).