summaryrefslogtreecommitdiff
path: root/drivers/hv/Makefile
diff options
context:
space:
mode:
authorKai Vehmanen <kai.vehmanen@linux.intel.com>2019-07-22 17:13:43 +0300
committerMark Brown <broonie@kernel.org>2019-07-23 14:18:18 +0300
commit04c8027764bc82a325d3abc6f39a6a4642a937cb (patch)
treebfa0eeaeebd596479a786025fad3e098ff42182f /drivers/hv/Makefile
parentf1b1b9b136827915624136624ff54aba5890a15b (diff)
downloadlinux-04c8027764bc82a325d3abc6f39a6a4642a937cb.tar.xz
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 <kai.vehmanen@linux.intel.com> Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com> Link: https://lore.kernel.org/r/20190722141402.7194-3-pierre-louis.bossart@linux.intel.com Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'drivers/hv/Makefile')
0 files changed, 0 insertions, 0 deletions