[PATCH 4.1 22/84] dmaengine: pl330: Really fix choppy sound because of wrong residue calculation
From: Greg Kroah-Hartman
Date: Fri Aug 14 2015 - 13:49:47 EST
4.1-stable review patch. If anyone has any objections, please let me know.
From: Krzysztof Kozlowski <k.kozlowski.k@xxxxxxxxx>
commit 5dd90e5b91e0f5c925b12b132c7cd27538870256 upstream.
When pl330 driver was used during sound playback, after some time or
after a number of plays the sound became choppy or totally noisy. For
example on Odroid XU3 board the first four executions of aplay with
small WAVE worked fine, but fifth was unrecognizable with errors:
$ aplay /usr/share/sounds/alsa/Front_Right.wava
underrun!!! (at least 0.095 ms long)
Issue was caused by wrong residue reported by pl330 driver to
pcm_dmaengine for its cyclic dma transfers.
The pl330_tx_status(), residue reporting function, used a "last" flag in
a descriptor to indicate that there is no more data to send.
The pl330_tx_submit() iterated over descriptors trying to remove this
flag from them and then mark last descriptor as "last". However when
iterating it actually removed the flag not from descriptors but always
from last of it (and then reset it). Thus effectively once some
descriptor was marked as last, then it stayed like this forever causing
residue to be reported too low.
Signed-off-by: Krzysztof Kozlowski <k.kozlowski.k@xxxxxxxxx>
Fixes: aee4d1fac887 ("dmaengine: pl330: improve pl330_tx_status() function")
Suggested-by: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx>
Tested-by: Lars-Peter Clausen <lars@xxxxxxxxxx>
Signed-off-by: Vinod Koul <vinod.koul@xxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
drivers/dma/pl330.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
@@ -2328,7 +2328,7 @@ static dma_cookie_t pl330_tx_submit(stru
desc->txd.callback = last->txd.callback;
desc->txd.callback_param = last->txd.callback_param;
- last->last = false;
+ desc->last = false;
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/