From: Qiao Zhou <zhouqiao@marvell.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>,
"haojian.zhuang@gmail.com" <haojian.zhuang@gmail.com>,
"zhangfei.gao@gmail.com" <zhangfei.gao@gmail.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>
Subject: Re: [PATCH] ASoC: mmp-pcm: config pcm slave via generic dmaengine
Date: Wed, 18 Dec 2013 13:55:26 +0800 [thread overview]
Message-ID: <52B138CE.3000800@marvell.com> (raw)
In-Reply-To: <52B062EC.2050605@metafoo.de>
On 12/17/2013 10:42 PM, Lars-Peter Clausen wrote:
> On 12/17/2013 01:49 PM, Mark Brown wrote:
>> On Tue, Dec 17, 2013 at 04:22:24PM +0800, Qiao Zhou wrote:
>>> use snd_dmaengine_pcm_prepare_slave_config to set slave config,
>>> and remove the max_burst_size = 4 hard code.
>>>
>>> select SND_SOC_GENERIC_DMAENGINE_PCM for mmp-pcm.
>>
>> Applied, thanks. Can you also convert to use snd_dmaengine_pcm_register()
>> and remove this file completely?
>>
>
> The problem here is that the driver uses sram for its audio memory and the
> platform has a custom function for looking up the sram pool. What we really
> need is a generic version of that which we can use in memalloc.c in the core.
>
> - Lars
>
I'll check the general memalloc implementation. Thanks.
--
Best Regards
Qiao
next prev parent reply other threads:[~2013-12-18 5:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 8:22 [PATCH] ASoC: mmp-pcm: config pcm slave via generic dmaengine Qiao Zhou
2013-12-17 12:49 ` Mark Brown
2013-12-17 14:42 ` Lars-Peter Clausen
2013-12-17 21:38 ` Mark Brown
2013-12-18 5:55 ` Qiao Zhou [this message]
2013-12-18 9:16 ` Lars-Peter Clausen
2013-12-18 10:20 ` Takashi Iwai
2013-12-18 11:03 ` Mark Brown
2013-12-18 10:14 ` Lars-Peter Clausen
2013-12-18 11:20 ` 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=52B138CE.3000800@marvell.com \
--to=zhouqiao@marvell.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=haojian.zhuang@gmail.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=zhangfei.gao@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.