diff options
| author | Sven Peter <sven@kernel.org> | 2026-08-29 10:08:38 +0200 |
|---|---|---|
| committer | Mika Westerberg <mika.westerberg@linux.intel.com> | 2026-09-01 10:12:41 +0200 |
| commit | 0b457c6733f73421a3fb03786f13d67c618b5119 (patch) | |
| tree | 39e3dc9b073773d9b0087cbb0b2b5325dae24060 /tools/lib/python/kdoc/python_version.py | |
| parent | c222f80be55f6c17851af1c68a70ae4046c848e2 (diff) | |
| download | linux-next-0b457c6733f73421a3fb03786f13d67c618b5119.tar.gz linux-next-0b457c6733f73421a3fb03786f13d67c618b5119.zip | |
thunderbolt: Tear down inactive DP tunnels when the domain is stopped
tb_stop() only tears down DMA tunnels so a DP tunnel that is still
waiting for dprx_work to complete keeps that work queued while the
routers are removed and the control channel is stopped. The work only
stops once the DPRX timeout has passed and because it requeues itself
until then the flush_workqueue() in tb_domain_remove() won't wait for its
final run. The callback then runs against a domain that is already torn
down. A reference to that domain is kept so the completion waiting for
that domain to disappear in unbind will block until the timeout is
eventually reached.
Tear down DP tunnels that are not active yet as well which also cancels
that work. Tunnels for displays that are already alive are untouched and
keep working.
Fixes: d6d458d42e1e ("thunderbolt: Handle DisplayPort tunnel activation asynchronously")
Cc: stable@vger.kernel.org
Signed-off-by: Sven Peter <sven@kernel.org>
Signed-off-by: Mika Westerberg <mika.westerberg@linux.intel.com>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions