From: Bo Shen <voice.shen@atmel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, devicetree-discuss@lists.ozlabs.org,
nicolas.ferre@atmel.com, linux-sound@vger.kernel.org,
plagnioj@jcrosoft.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] ASoC: atmel-pcm: add dma support
Date: Mon, 26 Nov 2012 10:04:28 +0800 [thread overview]
Message-ID: <50B2CE2C.4080700@atmel.com> (raw)
In-Reply-To: <20121123142747.GP4529@opensource.wolfsonmicro.com>
Hi Mark,
On 11/23/2012 22:27, Mark Brown wrote:
> On Fri, Nov 23, 2012 at 02:14:17PM +0800, Bo Shen wrote:
>> Add dmaengine specific routines and replace PDC ones in
>> pcm_ops if appropriate.
>>
>> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>> [voice.shen@atmel.com: adapt to soc dmaengine framework]
>> Signed-off-by: Bo Shen <voice.shen@atmel.com>
>
> Why is this not just two separate drivers?
I am not sure I got your means.
As I understand, I should keep the driver using pdc and won't touch it.
And create new a new driver using dma, am I right?
or else, ...?
Best Regards
Bo Shen
next prev parent reply other threads:[~2012-11-26 2:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-23 6:14 [PATCH 0/3] ASoC: atmel-pcm: add dma support Bo Shen
2012-11-23 6:14 ` [PATCH 1/3] ASoC: snd_dmaengine_pcm: add inline empty function Bo Shen
2012-11-23 6:14 ` [PATCH 2/3] ASoC: atmel-pcm: prepare for adding dma support Bo Shen
2012-11-23 6:14 ` [PATCH 3/3] ASoC: atmel-pcm: add " Bo Shen
2012-11-23 14:27 ` Mark Brown
2012-11-26 2:04 ` Bo Shen [this message]
2012-11-26 9:36 ` Mark Brown
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=50B2CE2C.4080700@atmel.com \
--to=voice.shen@atmel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sound@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.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).