[alsa-devel] [RFC][PATCH 0/3] Enhance ASoC on OMAP1510 by implementing DMA channel linking
jkrzyszt at tis.icnet.pl
Mon Aug 10 10:49:49 CEST 2009
Current implementation of ASoC OMAP PCM makes use of DMA channel self linking
feature for all machines but OMAP1510. This is caused by channel linking not
supported on OMAP1510 in current OMAP DMA implementation. Instead, DMA
interrputs are counted as periods, and after all periods in a buffer has been
detected, DMA transfer is started again for a new buffer content. The period
counter is also used as a software replacement for a hardware DMA progress
counter that has been found unusable on OMAP1510 in case of playback.
In my attempts to debug random PCM hangups, I was wondering what could happen
if a single interrupt was missing, ie. the period index was not incremented
for a period. It seems that the transfer would just hang after the current
buffer processed, as DMA would not be started again, waiting for a
Furthermore, software calculated PCM pointer accuracy can suffer from missing
Even if OMAP1510 DMA hardware does not support channel linking in a way like
newer models do, it has some other features that could be used for the
Interrupt status flags, passed to OMAP PCM interrupt handler routine, can be
used to get more accurate DMA progress counter software calculation.
Even if these enhancements did not help me in eliminating random PCM hangups
completely, I find them worth of sharing.
There are three patches in the series:
[RFC][PATCH 1/3] ARM: OMAP: DMA: Add support for DMA channel self linking on OMAP1510
[RFC][PATCH 2/3] ASoC: OMAP: Make use of DMA channel self linking on OMAP1510
[RFC][PATCH 3/3] ASoC: OMAP: Enhance OMAP1510 DMA progress software counter
Created against linux-2.6.31-rc5.
Tested on Amstrad Delta.
Signed-off-by: Janusz Krzysztofik <jkrzyszt at tis.icnet.pl>
More information about the Alsa-devel