summaryrefslogtreecommitdiff
path: root/Documentation/mailbox.txt
diff options
context:
space:
mode:
authorPierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>2020-03-17 19:33:19 +0300
committerVinod Koul <vkoul@kernel.org>2020-03-19 10:13:04 +0300
commitaf4cc917826fd1fb5c84a2a0f675777920db9074 (patch)
tree487230b80b9d804beb6f4682d9e271c9b698606e /Documentation/mailbox.txt
parent0d667d01c40b2cb9141108951890b9b27ea32584 (diff)
downloadlinux-af4cc917826fd1fb5c84a2a0f675777920db9074.tar.xz
soundwire: cadence: mask Slave interrupt before stopping clock
Intel QA reported a very rare case, possibly hardware-dependent, where a Slave can become UNATTACHED during a clock stop sequence, which leads to timeouts and failed suspend sequences. This patch suppresses the handling of all Slave events while this transition happens. The two cases that matter are: a) alerts: if the Slave wants to signal an alert condition, it can do so using the in-band wake, so there's almost no impact with this patch. b) sync loss or imp-def reset: in those cases, bringing back the Slave to functional state requires a complete re-enumeration. It's better to just ignore this case and restart cleanly, rather than attempt a 'clean' suspend. Validation results show the timeouts no longer visible with this patch. GitHub issue: https://github.com/thesofproject/linux/issues/1678 Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com> Link: https://lore.kernel.org/r/20200317163329.25501-8-pierre-louis.bossart@linux.intel.com Signed-off-by: Vinod Koul <vkoul@kernel.org>
Diffstat (limited to 'Documentation/mailbox.txt')
0 files changed, 0 insertions, 0 deletions