From: Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: Hongbo Zhang <hongbo.zhang-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Cc: vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
vakul-KZfg59tc24xl57MIdRCFDg@public.gmane.org,
djbw-b10kYP2dOMg@public.gmane.org,
linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH 2/2] DMA: Freescale: update driver to support 8-channel DMA engine
Date: Wed, 3 Jul 2013 11:41:31 -0500 [thread overview]
Message-ID: <1372869691.8183.130@snotra> (raw)
In-Reply-To: <51D39EE0.1040901-KZfg59tc24xl57MIdRCFDg@public.gmane.org> (from hongbo.zhang-KZfg59tc24xl57MIdRCFDg@public.gmane.org on Tue Jul 2 22:47:44 2013)
On 07/02/2013 10:47:44 PM, Hongbo Zhang wrote:
> On 07/03/2013 07:13 AM, Scott Wood wrote:
>> Wait a second -- how are we even getting into this code on these new
>> DMA controllers? All 85xx-family DMA controllers use
>> fsldma_chan_irq directly.
>>
> Right, we are using fsldma_chan_irq, this code never run.
> I just see there is such code for elo/eloplus DMA controllers, so I
> update it for the new 8-channel DMA.
That code is used for elo (e.g. mpc83xx DMA), but not eloplus.
-Scott
prev parent reply other threads:[~2013-07-03 16:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1372806786.8183.127@snotra>
2013-07-03 3:47 ` [PATCH 2/2] DMA: Freescale: update driver to support 8-channel DMA engine Hongbo Zhang
[not found] ` <51D39EE0.1040901-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2013-07-03 16:41 ` Scott Wood [this message]
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=1372869691.8183.130@snotra \
--to=scottwood-kzfg59tc24xl57midrcfdg@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=djbw-b10kYP2dOMg@public.gmane.org \
--cc=hongbo.zhang-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=vakul-KZfg59tc24xl57MIdRCFDg@public.gmane.org \
--cc=vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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).