From: Timur Tabi <timur@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Scott Wood <scottwood@freescale.com>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] Add docs for Freescale DMA & DMA channel device tree nodes
Date: Tue, 22 Jan 2008 15:30:03 -0600 [thread overview]
Message-ID: <4796605B.2000807@freescale.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0801221511540.24873@blarg.am.freescale.net>
Kumar Gala wrote:
> Signed-off-by: Zhang Wei <wei.zhang@freescale.com>
> Signed-off-by: Ebony Zhu <ebony.zhu@freescale.com>
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> ---
>
> Guys please review and make sure I got all your previous comments fixed
> up. I've added cell-index. and the examples should represent real HW.
>
> Documentation/powerpc/booting-without-of.txt | 128 ++++++++++++++++++++++++++
> 1 files changed, 128 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/powerpc/booting-without-of.txt b/Documentation/powerpc/booting-without-of.txt
> index da98154..3584c33 100644
> --- a/Documentation/powerpc/booting-without-of.txt
> +++ b/Documentation/powerpc/booting-without-of.txt
> @@ -2615,6 +2615,134 @@ platforms are moved over to use the flattened-device-tree model.
> - clock-frequency : The frequency of the input clock, which typically
> comes from an on-board dedicated oscillator.
>
> + * Freescale 83xx DMA Controller
> +
> + Freescale PowerPC 83xx have on chip general purpose DMA controllers.
> +
> + Required properties:
> +
> + - compatible : compatible list, contains 2 entries, first is
> + "fsl,CHIP-dma", where CHIP is the processor
> + (mpc8349, mpc8360, etc.) and the second is
> + "fsl,elo-dma"
> + - reg : <registers mapping for DMA general status reg>
> + - ranges : Should be defined as specified in 1) to describe the
> + DMA controller channels.
What does "Should be defined as specified in 1)" mean?
> + - cell-index : controller index. 0 for controller @ 0x8100
This should be more generic. I believe for each of our SoCs, we designation one
DMA controller to be "DMA Controller 1", and that one should have a cell-index
of "0".
> + - interrupts : <interrupt mapping for DMA IRQ>
> + - interrupt-parent : optional, if needed for interrupt mapping
On 83xx, all DMA channels share the same interrupt? Couldn't we just specify
the same IRQ in each channel's node, so that they look the same across 83xx,
85xx, and 86xx? My sound driver doesn't use Extended Mode, but it does check
for "fsl,8610-dma-channel". I'm thinking that maybe I should change to to look
for "elo" or "eloplus", but it would be nice if we could make the DMA node for
an 86xx SoC compatible with a driver that expects "fsl,elo-dma-channel".
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-01-22 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 21:13 [PATCH] [POWERPC] Add docs for Freescale DMA & DMA channel device tree nodes Kumar Gala
2008-01-22 21:30 ` Timur Tabi [this message]
2008-01-22 21:48 ` Scott Wood
2008-01-22 22:00 ` Kumar Gala
2008-01-22 22:02 ` 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=4796605B.2000807@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).