diff options
| author | Kai Vehmanen <[email protected]> | 2019-07-22 09:13:43 -0500 |
|---|---|---|
| committer | Mark Brown <[email protected]> | 2019-07-23 12:18:18 +0100 |
| commit | 04c8027764bc82a325d3abc6f39a6a4642a937cb (patch) | |
| tree | bfa0eeaeebd596479a786025fad3e098ff42182f /tools/perf/scripts/python/bin/stackcollapse-report | |
| parent | f1b1b9b136827915624136624ff54aba5890a15b (diff) | |
ASoC: SOF: reset DMA state in prepare
When application goes through SUSPEND/STOP->PREPARE->START
cycle, we should always reprogram the SOF device to start
DMA from a known state so that hw_ptr/appl_ptrs remain valid.
This is expected by ALSA core as it resets the buffer
state as part of prepare (see snd_pcm_do_prepare()).
Fix the issue by forcing reconfiguration of the FW with
STREAM_PCM_PARAMS in prepare(). Use combined logic to handle
prepare and the existing flow to reprogram hw-params after
system suspend.
Without the fix, first call to pcm pointer() will return
an invalid hw_ptr and application may immediately observe XRUN
status, unless "start_threshold" SW parameter is set to maximum
value by the application.
Signed-off-by: Kai Vehmanen <[email protected]>
Signed-off-by: Pierre-Louis Bossart <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Mark Brown <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-report')
0 files changed, 0 insertions, 0 deletions