From: Scott Wood <scottwood@freescale.com>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [POWERPC] Add docs for Freescale DMA & DMA channel device tree nodes
Date: Tue, 22 Jan 2008 15:48:30 -0600 [thread overview]
Message-ID: <479664AE.9060107@freescale.com> (raw)
In-Reply-To: <4796605B.2000807@freescale.com>
Timur Tabi wrote:
> On 83xx, all DMA channels share the same interrupt?
Yes.
> Couldn't we just
> specify the same IRQ in each channel's node, so that they look the same
> across 83xx, 85xx, and 86xx?
The consensus that I thought we had reached was to let 83xx specify the
interrupt in the controller node (to make things simple for a driver
using the shared summary register rather than registering four handlers
for the same IRQ), but require that it also be in the channel node, and
that if there is an interrupt in the controller node, that it be the
same as in all the channels.
> 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".
Sure it'd be nice, but it's not possible without going back in time and
convincing the hardware people to make them 100% compatible.
-Scott
next prev parent reply other threads:[~2008-01-22 21:48 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
2008-01-22 21:48 ` Scott Wood [this message]
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=479664AE.9060107@freescale.com \
--to=scottwood@freescale.com \
--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).