2015-06-13 14:47 GMT+09:00 Krzysztof Kozlowski <k.kozlowski@xxxxxxxxxxx>:
> W dniu 13.06.2015 o 06:48, gabriel@xxxxxxxxx pisze:
>> On 06/10/2015 10:22 AM, Krzysztof Kozlowski wrote:
>>>
>>> Gabriel,
>>>
>>> I sent a patch which should fix the issue. Could you give it a try? Of
>>> course don't revert the other patches and don't use other workarounds.
>>> Just apply the patch on clean (vanilla would be the best) kernel.
>>> [RFT PATCH] dmaengine: Fix choppy sound because of unimplemented resume
>>>
>>
>> hi krzysztof,
>>
>> thanks a lot for your work. having only that patch applied unfortunately
>> brought back the problem after something more than one day. the sound
>> became choppy/noisy again. I will now compile the -next kernel and give
>> it a try.
>
> Thanks, I'll try to reproduce the issue on my Odroid. Can you share more
> details how to reproduce it? The audio must play continuously or just
> from time to time but the board must be turned on for more than one day?
I bought some audio cables and successfully reproduced similar issue
(choppy sound) on Odroid XU3-Lite. On current linux-next
(next-20150612) the sound is awful (choppy) after few seconds of play.
For example first four of:
$ aplay /usr/share/sounds/alsa/Front_Right.wav
work fine. But then it just gets worse and underruns are reported:
$ Playing WAVE '/usr/share/sounds/alsa/Front_Right.wav' : Signed 16
bit Little Endian, Rate 48000 Hz, Mono
$ underrun!!! (at least 0.095 ms long)
Reverting the commit aee4d1fac887 ("dmaengine: pl330: improve
pl330_tx_status() function") fixes this issue so this is not related
to missing "resume" function. At least this particular issue on my
Odroid is not related to missing resume but I did not try to play
sound for 24 hours.
My fix does not solve this. Probably "cc-stable" and "fixes" tags
should be dropped.
Anyway I'll try to investigate it more. If anyone has any ideas, please share.
Best regards,
Krzysztof
--
To unsubscribe from this list: send the line "unsubscribe dmaengine" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
