aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
diff options
context:
space:
mode:
authorLoic Poulain <[email protected]>2025-05-22 13:17:04 +0000
committerJeff Johnson <[email protected]>2025-06-07 14:36:01 +0000
commitdc9c4252fe0d7a7f1ee904405ea91534277305bf (patch)
tree4c51e5bef2ca88897fda32fe6a4334150b2236c9 /drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c
parentath10k: snoc: fix unbalanced IRQ enable in crash recovery (diff)
downloadkernel-dc9c4252fe0d7a7f1ee904405ea91534277305bf.tar.gz
kernel-dc9c4252fe0d7a7f1ee904405ea91534277305bf.zip
wifi: ath10k: Avoid vdev delete timeout when firmware is already down
In some scenarios, the firmware may be stopped before the interface is removed, either due to a crash or because the remoteproc (e.g., MPSS) is shut down early during system reboot or shutdown. This leads to a delay during interface teardown, as the driver waits for a vdev delete response that never arrives, eventually timing out. Example (SNOC): $ echo stop > /sys/class/remoteproc/remoteproc0/state [ 71.64] remoteproc remoteproc0: stopped remote processor modem $ reboot [ 74.84] ath10k_snoc c800000.wifi: failed to transmit packet, dropping: -108 [ 74.84] ath10k_snoc c800000.wifi: failed to submit frame: -108 [...] [ 82.39] ath10k_snoc c800000.wifi: Timeout in receiving vdev delete response To avoid this, skip waiting for the vdev delete response if the firmware is already marked as unreachable (`ATH10K_FLAG_CRASH_FLUSH`), similar to how `ath10k_mac_wait_tx_complete()` and `ath10k_vdev_setup_sync()` handle this case. Signed-off-by: Loic Poulain <[email protected]> Link: https://patch.msgid.link/[email protected] Signed-off-by: Jeff Johnson <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c')
0 files changed, 0 insertions, 0 deletions