All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Nikula <jarkko.nikula@bitmer.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: alsa-devel@alsa-project.org,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: omap-pcm: Fix the no period wakeup implementation
Date: Tue, 04 Oct 2011 11:34:28 +0300	[thread overview]
Message-ID: <4E8AC514.1030002@bitmer.com> (raw)
In-Reply-To: <1317715792-30279-1-git-send-email-peter.ujfalusi@ti.com>

On 10/04/2011 11:09 AM, Peter Ujfalusi wrote:
> After omap_request_dma the BLOCK_IRQ is enabled as default
> configuration for the channel.
> If we are requested for no period wakeup, we need to disable
> the BLOCK_IRQ in order to not receive any interrupts.
>
> Signed-off-by: Peter Ujfalusi<peter.ujfalusi@ti.com>
> ---
>   sound/soc/omap/omap-pcm.c |    8 ++++++++
>   1 files changed, 8 insertions(+), 0 deletions(-)
>
> diff --git a/sound/soc/omap/omap-pcm.c b/sound/soc/omap/omap-pcm.c
> index 9b5c88a..5e37ec9 100644
> --- a/sound/soc/omap/omap-pcm.c
> +++ b/sound/soc/omap/omap-pcm.c
> @@ -198,6 +198,14 @@ static int omap_pcm_prepare(struct snd_pcm_substream *substream)
>   			      OMAP_DMA_LAST_IRQ | OMAP_DMA_BLOCK_IRQ);
>   	else if (!substream->runtime->no_period_wakeup)
>   		omap_enable_dma_irq(prtd->dma_ch, OMAP_DMA_FRAME_IRQ);
> +	else {
> +		/*
> +		 * No period wakeup:
> +		 * we need to disable BLOCK_IRQ, which is enabled by the omap
> +		 * dma core at request dma time.
> +		 */
> +		omap_disable_dma_irq(prtd->dma_ch, OMAP_DMA_BLOCK_IRQ);
> +	}
>
Acked-by: Jarkko Nikula <jarkko.nikula@bitmer.com>

while it would be more clear to fix this in omap dma core.

  reply	other threads:[~2011-10-04  8:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-04  8:09 [PATCH] ASoC: omap-pcm: Fix the no period wakeup implementation Peter Ujfalusi
2011-10-04  8:34 ` Jarkko Nikula [this message]
2011-10-04  9:02   ` Péter Ujfalusi
2011-10-04 11:04 ` 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=4E8AC514.1030002@bitmer.com \
    --to=jarkko.nikula@bitmer.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@ti.com \
    --cc=peter.ujfalusi@ti.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.