From: Timur Tabi <timur@freescale.com>
To: Scott Wood <scottwood@freescale.com>,
Kumar Gala <galak@kernel.crashing.org>,
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:51:58 -0600 [thread overview]
Message-ID: <4744D2AE.60902@freescale.com> (raw)
In-Reply-To: <20071121222822.GB19445@localhost.localdomain>
David Gibson wrote:
> Indeed, indexing or writing into shared registers is exactly what
> cell-index is for.
I don't care whether it's cell-index or device-id, but I need to know which
DMA controller is #0 and which one is #1, and I need to know which channel is
#0, which one is #1, etc. Dividing register offsets by 0x80 is not
acceptable, because what if we have an elo-plus-plus that has 0x100 bytes per
register, where the additional 0x20 bytes are for enhanced features?
--
Timur Tabi
Linux Kernel Developer @ Freescale
next prev parent reply other threads:[~2007-11-22 0:50 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 [this message]
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=4744D2AE.60902@freescale.com \
--to=timur@freescale.com \
--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).