From: Jarkko Nikula <jhnikula@gmail.com>
To: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Tony Lindgren <tony@atomide.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Peter Ujfalusi <peter.ujfalusi@nokia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.arm.linux.org.uk"
<linux-arm-kernel@lists.arm.linux.org.uk>
Subject: Re: [RFC][PATCH 3/3 v2] ASoC: OMAP: Enhance OMAP1510 DMA progress software counter
Date: Tue, 11 Aug 2009 09:42:48 +0300 [thread overview]
Message-ID: <20090811094248.3b869f09.jhnikula@gmail.com> (raw)
In-Reply-To: <200908110107.11485.jkrzyszt@tis.icnet.pl>
On Tue, 11 Aug 2009 01:07:10 +0200
Janusz Krzysztofik <jkrzyszt@tis.icnet.pl> wrote:
> Enhance period index accuracy, particularly just before buffer rewind, by
> making use of DMA interrupt status flags in addition to simply counting up
> interrupts.
>
> Corrections since v1:
> 1. Fix buggy DMA interrupt handling in case of multiple status flags set in
> parallel.
> 2. Enable OMAP_DMA_LAST_IRQ only for playback on OMAP1510.
>
> This patch applies on top of patch 2 from this series:
> [RFC][PATCH 2/3] ASoC: OMAP: Make use of DMA channel self linking on OMAP1510
>
> Created against linux-2.6.31-rc5.
>
> Tested on Amstrad Delta.
>
> Signed-off-by: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
>
> ---
> --- linux-2.6.31-rc5/sound/soc/omap/omap-pcm.c.orig 2009-08-10 22:41:25.000000000 +0200
> +++ linux-2.6.31-rc5/sound/soc/omap/omap-pcm.c 2009-08-10 23:15:46.000000000 +0200
> @@ -68,13 +68,27 @@ static void omap_pcm_dma_irq(int ch, u16
> * that can be used by omap_pcm_pointer() instead.
> */
> spin_lock_irqsave(&prtd->lock, flags);
> + if ((stat == OMAP_DMA_LAST_IRQ) &&
> + (prtd->period_index == runtime->periods - 1)) {
> + /* we are in sync, do nothing */
> + spin_unlock_irqrestore(&prtd->lock, flags);
> + return;
> + }
> if (prtd->period_index >= 0) {
> - if (++prtd->period_index == runtime->periods) {
> + if (stat & OMAP_DMA_BLOCK_IRQ) {
> + /* end of buffer reached, loop back */
> + prtd->period_index = 0;
> + } else if (stat & OMAP_DMA_LAST_IRQ) {
> + /* update the counter for the last period */
> + prtd->period_index = runtime->periods - 1;
> + } else if (++prtd->period_index >= runtime->periods) {
> + /* end of buffer missed? loop back */
> prtd->period_index = 0;
> }
> }
> spin_unlock_irqrestore(&prtd->lock, flags);
> - }
> + } else if (stat == OMAP_DMA_LAST_IRQ)
> + return;
>
Is this test needed? This interrupt is set only for playback on
omap1510 so this looks null-op.
> snd_pcm_period_elapsed(substream);
> }
> @@ -175,7 +189,12 @@ static int omap_pcm_prepare(struct snd_p
> dma_params.frame_count = runtime->periods;
> omap_set_dma_params(prtd->dma_ch, &dma_params);
>
> - omap_enable_dma_irq(prtd->dma_ch, OMAP_DMA_FRAME_IRQ);
> + if ((cpu_is_omap1510()) &&
> + (substream->stream == SNDRV_PCM_STREAM_PLAYBACK))
> + omap_enable_dma_irq(prtd->dma_ch, OMAP_DMA_FRAME_IRQ |
> + OMAP_DMA_LAST_IRQ);
Indent OMAP_DMA_LAST_IRQ with tab(s) and spaces to the same column
than OMAP_DMA_FRAME_IRQ. Looks nicer then. Should the
OMAP_DMA_BLOCK_IRQ to be set since it is handled in omap_pcm_dma_irq?
--
Jarkko
next prev parent reply other threads:[~2009-08-11 6:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 8:50 [RFC] [PATCH 3/3] ASoC: OMAP: Enhance OMAP1510 DMA progress software counter Janusz Krzysztofik
2009-08-10 9:43 ` Janusz Krzysztofik
2009-08-10 21:11 ` Janusz Krzysztofik
2009-08-10 23:07 ` [RFC][PATCH 3/3 v2] " Janusz Krzysztofik
2009-08-11 6:42 ` Jarkko Nikula [this message]
2009-08-11 9:30 ` Janusz Krzysztofik
2009-08-11 19:44 ` [PATCH 3/3 v3] " Janusz Krzysztofik
2009-08-17 9:26 ` Jarkko Nikula
2009-08-17 10:03 ` Mark Brown
2009-08-18 13:42 ` Janusz Krzysztofik
2009-08-18 13:45 ` Mark Brown
2009-08-18 16:57 ` Jarkko Nikula
2009-08-24 12:50 ` Tony Lindgren
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=20090811094248.3b869f09.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=jkrzyszt@tis.icnet.pl \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=peter.ujfalusi@nokia.com \
--cc=tony@atomide.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