alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Kukjin Kim <kgene.kim@samsung.com>
To: 'Mark Brown' <broonie@opensource.wolfsonmicro.com>,
	'Liam Girdwood' <lrg@ti.com>,
	'Boojin Kim' <boojin.kim@samsung.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] ASoC: Flush Samsung DMA on free
Date: Tue, 27 Sep 2011 09:05:15 +0900	[thread overview]
Message-ID: <003b01cc7ca9$228b3f10$67a1bd30$%kim@samsung.com> (raw)
In-Reply-To: <1316557614-32044-1-git-send-email-broonie@opensource.wolfsonmicro.com>

Mark Brown wrote:
> 
> Ever since it was written the Samsung DMA driver has had a TODO in the
> hw_free() function wondering if we need to flush the DMA buffers. Up until
> now the answer has been no but with the recent improvements Boojin has
> done to the DMA infrastructure for the Samsung port the answer has changed
> to yes for at least S3C6410 systems.
> 
> If we don't then when we next prepare() the channel the API will get
> confused trying to run callbacks on the transfers hanging around from the
> previous time the stream was open and oops.
> 
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
> 
> Kukjin, this should probably get added to your branch assuming it's OK
> for other CPUs.
> 
Looks ok to me, applied.
Thanks.

Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@samsung.com>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.

>  sound/soc/samsung/dma.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/sound/soc/samsung/dma.c b/sound/soc/samsung/dma.c
> index 851346f..2d622b6 100644
> --- a/sound/soc/samsung/dma.c
> +++ b/sound/soc/samsung/dma.c
> @@ -198,10 +198,10 @@ static int dma_hw_free(struct snd_pcm_substream
> *substream)
> 
>  	pr_debug("Entered %s\n", __func__);
> 
> -	/* TODO - do we need to ensure DMA flushed */
>  	snd_pcm_set_runtime_buffer(substream, NULL);
> 
>  	if (prtd->params) {
> +		prtd->params->ops->flush(prtd->params->ch);
>  		prtd->params->ops->release(prtd->params->ch,
>  					prtd->params->client);
>  		prtd->params = NULL;
> --
> 1.7.6.3

      parent reply	other threads:[~2011-09-27  0:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-20 22:26 [PATCH] ASoC: Flush Samsung DMA on free Mark Brown
     [not found] ` <005e01cc7853$7a3d5400$6eb7fc00$%kim@samsung.com>
2011-09-21 11:51   ` Kukjin Kim
2011-09-27  0:05 ` Kukjin Kim [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='003b01cc7ca9$228b3f10$67a1bd30$%kim@samsung.com' \
    --to=kgene.kim@samsung.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=boojin.kim@samsung.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@ti.com \
    --cc=patches@opensource.wolfsonmicro.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).