From: Lars-Peter Clausen <lars@metafoo.de>
To: Jiada Wang <jiada_wang@mentor.com>, perex@perex.cz, tiwai@suse.com
Cc: alsa-devel@alsa-project.org, apape@de.adit-jv.com,
linux-kernel@vger.kernel.org
Subject: Re: [alsa-devel] [PATCH v2 1/1] ALSA: SOC: DMA: access buffer pointer atomically
Date: Thu, 1 Dec 2016 13:49:26 +0100 [thread overview]
Message-ID: <d8dbe0cb-ca98-6030-5977-181f09b8e1c1@metafoo.de> (raw)
In-Reply-To: <20161201052422.18775-1-jiada_wang@mentor.com>
On 12/01/2016 06:24 AM, Jiada Wang wrote:
> From: Andreas Pape <apape@de.adit-jv.com>
>
> Setting pointer and afterwards check for wrap around leads
> to the possibility of returning the inconsistent pointer position.
>
> This patch accesses buffer pointer atomically to avoid this issue.
>
> v2: use READ_ONCE and WRITE_ONCE to ensure read/write of buffer pointer in
> only one access
> also updates snd_dmaengine_pcm_pointer_no_residue to ensure atomic
> access
>
> Signed-off-by: Andreas Pape <apape@de.adit-jv.com>
> Signed-off-by: Jiada Wang <jiada_wang@mentor.com>
Thanks for the patch. Looks good to me.
Reviewed-by: Lars-Peter Clausen <lars@metafoo.de>
> ---
> sound/core/pcm_dmaengine.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/sound/core/pcm_dmaengine.c b/sound/core/pcm_dmaengine.c
> index 8eb58c7..b6255fd 100644
> --- a/sound/core/pcm_dmaengine.c
> +++ b/sound/core/pcm_dmaengine.c
> @@ -139,12 +139,14 @@ EXPORT_SYMBOL_GPL(snd_dmaengine_pcm_set_config_from_dai_data);
>
> static void dmaengine_pcm_dma_complete(void *arg)
> {
> + unsigned int new_pos;
> struct snd_pcm_substream *substream = arg;
> struct dmaengine_pcm_runtime_data *prtd = substream_to_prtd(substream);
>
> - prtd->pos += snd_pcm_lib_period_bytes(substream);
> - if (prtd->pos >= snd_pcm_lib_buffer_bytes(substream))
> - prtd->pos = 0;
> + new_pos = prtd->pos + snd_pcm_lib_period_bytes(substream);
> + if (new_pos >= snd_pcm_lib_buffer_bytes(substream))
> + new_pos = 0;
> + WRITE_ONCE(prtd->pos, new_pos);
>
> snd_pcm_period_elapsed(substream);
> }
> @@ -235,7 +237,7 @@ EXPORT_SYMBOL_GPL(snd_dmaengine_pcm_trigger);
> snd_pcm_uframes_t snd_dmaengine_pcm_pointer_no_residue(struct snd_pcm_substream *substream)
> {
> struct dmaengine_pcm_runtime_data *prtd = substream_to_prtd(substream);
> - return bytes_to_frames(substream->runtime, prtd->pos);
> + return bytes_to_frames(substream->runtime, READ_ONCE(prtd->pos));
> }
> EXPORT_SYMBOL_GPL(snd_dmaengine_pcm_pointer_no_residue);
>
>
prev parent reply other threads:[~2016-12-01 12:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 5:24 Jiada Wang
2016-12-01 12:49 ` 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=d8dbe0cb-ca98-6030-5977-181f09b8e1c1@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=apape@de.adit-jv.com \
--cc=jiada_wang@mentor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=tiwai@suse.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
all inboxes | Powered by JetHome®