From: Lars-Peter Clausen <lars@metafoo.de>
To: Bo Shen <voice.shen@atmel.com>
Cc: Elen Song <elen.song@atmel.com>, Mark Brown <broonie@kernel.org>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: atmel-pcm-dma: Remove SND_DMAENGINE_PCM_FLAG_NO_RESIDUE flag
Date: Tue, 07 Jan 2014 10:15:51 +0100 [thread overview]
Message-ID: <52CBC5C7.9090802@metafoo.de> (raw)
In-Reply-To: <52CBC359.7010906@atmel.com>
On 01/07/2014 10:05 AM, Bo Shen wrote:
> Hi Lars,
>
> On 01/06/2014 10:30 PM, Lars-Peter Clausen wrote:
>> Since commit d48de6f1a ("DMA: AT91: Get residual bytes in dma buffer") the
>> at91-dma driver has support for residue reporting. So there is no need to
>> specify the SND_DMAENGINE_PCM_FLAG_NO_RESIDUE flag. This allows for a finer
>> grained resolution of the PCM pointer as well as avoids the race condition
>> that
>> can occur with the period counting that is used when the dmaengine driver
>> does
>> not support residue reporting.
>>
>> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
>>
>> ---
>> I don't have the hardware, so only compile tested. It should work though
>> if the
>> residue calculation in the dma driver is implemented correctly.
>> ---
>> sound/soc/atmel/atmel-pcm-dma.c | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> Thanks for your patch.
>
> For the dma get residue code, we are improving it. So, I think we'd better
> waiting the improvement done and after let this patch go into mainline.
>
> What do you think?
If the residue reporting in the dmaengine driver doesn't work properly yet
we have to wait.
- Lars
prev parent reply other threads:[~2014-01-07 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 14:30 [PATCH] ASoC: atmel-pcm-dma: Remove SND_DMAENGINE_PCM_FLAG_NO_RESIDUE flag Lars-Peter Clausen
2014-01-07 9:05 ` Bo Shen
2014-01-07 9:15 ` Lars-Peter Clausen [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=52CBC5C7.9090802@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=elen.song@atmel.com \
--cc=lgirdwood@gmail.com \
--cc=nicolas.ferre@atmel.com \
--cc=voice.shen@atmel.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