summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorKang Yang <kang.yang@oss.qualcomm.com>2025-10-14 19:07:57 +0800
committerJeff Johnson <jeff.johnson@oss.qualcomm.com>2025-10-15 16:37:52 -0700
commitf35a07a4842a88801d9182b1a76d178bfa616978 (patch)
tree01826e90ac9b5524d46d176e49f071e31e4daf54 /tools/perf/scripts/python
parent4077d7fb27be990a8ddcff9b49f7e1788a960f3a (diff)
downloadlinux-f35a07a4842a88801d9182b1a76d178bfa616978.tar.gz
linux-f35a07a4842a88801d9182b1a76d178bfa616978.zip
wifi: ath10k: move recovery check logic into a new work
Currently, ath10k has a recovery check logic. It will wait for the last recovery to finish by wait_for_completion_timeout(); But in SDIO scenarios, the recovery function may be invoked from interrupt context, where long blocking waits are undesirable and can lead to system instability. Additionally, Linux’s ordered workqueue processes one task at a time. If a previous recovery is still queued or executing, new triggers are ignored. This prevents accurate tracking of consecutive failures and delays transition to the WEDGED state. To address this, move the recovery check logic into a different workqueue. Tested-on: QCA6174 hw3.2 PCI WLAN.RM.4.4.1-00288-QCARMSWPZ-1 Tested-on: QCA6174 hw3.2 SDIO WLAN.RMH.4.4.1-00189 Fixes: c256a94d1b1b ("wifi: ath10k: shutdown driver when hardware is unreliable") Signed-off-by: Kang Yang <kang.yang@oss.qualcomm.com> Reviewed-by: Baochen Qiang <baochen.qiang@oss.qualcomm.com> Link: https://patch.msgid.link/20251014110757.155-1-kang.yang@oss.qualcomm.com Signed-off-by: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions