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

Kumar Gala wrote:

>> Shouldn't we put some text somewhere that we're calling it the Elo 
>> controller even though that word isn't used in the reference manual?
> 
> we don't really have a place to put that.  its effectively documented 
> right here.

I still think we need something.  Otherwise, people are going to be confused. 
  I know I would.  I'd be searching the RM for the string "ELO" and wonder why 
it wasn't there.


>>> +  Example:
>>> +    dma@21000 {
>>
>> Shouldn't this be dma@21300?
> 
> its an example that has not basis is reality :)

Eh?

>> 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.

There isn't one.  Why should the driver assume that reg/80 == channel #? 
Besides, I still can't differentiate between DMA controller 0 and DMA 
controller 1 that way.  No, we need a device-id.

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

  parent reply	other threads:[~2007-11-22  0:47 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
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 [this message]
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=4744D1D0.70800@freescale.com \
    --to=timur@freescale.com \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).