From: Dong Aisheng <aisheng.dong@freescale.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Liam Girdwood <lrg@ti.com>, Vinod Koul <vinod.koul@intel.com>,
Ola Lilja <ola.o.lilja@stericsson.com>,
<alsa-devel@alsa-project.org>,
Russell King <linux@arm.linux.org.uk>,
Mika Westerberg <mika.westerberg@iki.fi>,
<linux-kernel@vger.kernel.org>, Shawn Guo <shawn.guo@linaro.org>
Subject: Re: [alsa-devel] [PATCH v2 2/3] ASoC: dmaengine-pcm: Rename and deprecate snd_dmaengine_pcm_pointer
Date: Wed, 20 Jun 2012 21:41:32 +0800 [thread overview]
Message-ID: <20120620134131.GK10387@shlinux2.ap.freescale.net> (raw)
In-Reply-To: <1339438302-12417-2-git-send-email-lars@metafoo.de>
On Mon, Jun 11, 2012 at 08:11:41PM +0200, Lars-Peter Clausen wrote:
> Currently the sound dmaengine pcm helper functions implement the pcm_pointer
> callback by trying to count the number of elapsed periods. This is done by
> advancing the stream position in the dmaengine callback by one period.
> Unfortunately there is no guarantee that the callback will be called for each
> elapsed period. It may be possible that under high system load it is only called
> once for multiple elapsed periods. This patch renames the current implementation
> and documents its shortcomings and that it should not be used anymore in new
> drivers.
>
> The next patch will introduce a new snd_dmaengine_pcm_pointer which will be
> implemented based on querying the current stream position from the dma device.
>
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
>
Acked-by: Dong Aisheng <dong.aisheng@linaro.org>
> ---
> If you are maintaining a pcm driver which use the dmaengine pcm helper please
> check if you platform works with the new snd_dmaengine_pcm_pointer
> implementation which is added in the next patch (ux500 seems to be good
> candidate). And if it does send a follow-up patch to convert your platform to
> the new implementation. If it does not please try to fix or add residue
> reporting support to your dmaengine driver.
>
Will try it after adding cyclic tx_status support for mxs/imx dma driver.
Regards
Dong Aisheng
next prev parent reply other threads:[~2012-06-20 13:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 18:11 [PATCH v2 1/3] dmaengine: Add wrapper for device_tx_status callback Lars-Peter Clausen
2012-06-11 18:11 ` [PATCH v2 2/3] ASoC: dmaengine-pcm: Rename and deprecate snd_dmaengine_pcm_pointer Lars-Peter Clausen
2012-06-20 10:55 ` Vinod Koul
2012-06-20 13:41 ` Dong Aisheng [this message]
2012-06-11 18:11 ` [PATCH v2 3/3] ASoC: dmaengine-pcm: Add support for querying stream position from DMA driver Lars-Peter Clausen
2012-06-20 10:55 ` Vinod Koul
2012-06-20 13:48 ` [alsa-devel] " Dong Aisheng
2012-06-20 14:11 ` Lars-Peter Clausen
2012-06-20 10:54 ` [PATCH v2 1/3] dmaengine: Add wrapper for device_tx_status callback Vinod Koul
2012-06-20 12:13 ` Lars-Peter Clausen
2012-06-20 13:09 ` Mark Brown
2012-06-20 13:37 ` Vinod Koul
2012-06-20 13:35 ` Vinod Koul
2012-06-20 14:40 ` 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=20120620134131.GK10387@shlinux2.ap.freescale.net \
--to=aisheng.dong@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lrg@ti.com \
--cc=mika.westerberg@iki.fi \
--cc=ola.o.lilja@stericsson.com \
--cc=shawn.guo@linaro.org \
--cc=vinod.koul@intel.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
Powered by JetHome