summaryrefslogtreecommitdiff
path: root/tools/lib/python
diff options
context:
space:
mode:
authorMark Brown <broonie@kernel.org>2026-10-04 21:51:55 +0200
committerMark Brown <broonie@kernel.org>2026-10-04 21:51:55 +0200
commit27d0ec1e012eb8f4b66076ef33989334769cb1c2 (patch)
treed1bb76bcb660b100609e869cc36ea0b2f583ff9f /tools/lib/python
parent6158ac6cbe6b0bb464cdff60096d91c0a469e786 (diff)
parent9d29132d81a7f269177be676c3b81cc575899975 (diff)
ASoC: rt-sdw: always cancel jack work on remove
Jiale Yao <yaojiale02@163.com> says: The Realtek SoundWire codec remove callbacks cancel jack work only while hw_init is true. hw_init is cleared by update_status() when the slave becomes unattached, but jack work can already have been queued by the interrupt callback or jack initialization path. If remove runs after that state transition, the pending work is not drained and can run after the codec private data has been freed. The same lifecycle problem can be triggered in each codec: 1. init queues jack work; 2. update_status(UNATTACHED) clears hw_init; 3. remove sees hw_init false and skips the cancel; 4. the work runs after private data teardown. Each codec initializes its work objects during probe, so the remove paths can cancel them unconditionally and pair the work lifetime with the codec private data lifetime instead of the mutable hw_init state. The series fixes rt5682-sdw, rt711-sdw, rt711-sdca-sdw, rt712-sdca-sdw, rt721-sdca-sdw and rt722-sdca-sdw. Each patch is independent and applies to the same baseline. Link: https://patch.msgid.link/20260925145019.2290367-1-yaojiale02@163.com
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions