diff options
| author | Seevalamuthu Mariappan <quic_seevalam@quicinc.com> | 2022-02-17 09:26:35 +0300 |
|---|---|---|
| committer | Kalle Valo <quic_kvalo@quicinc.com> | 2022-02-21 13:28:17 +0300 |
| commit | a19c0e104db95f78540982c64d78217cd9830d72 (patch) | |
| tree | 2b0532c6ad81a71e68a65f77cc7ff7be3510fa2b /tools/perf/scripts/python/stackcollapse.py | |
| parent | f2180ccb52b5fd0876291ad2df37e2898cac18cf (diff) | |
| download | linux-a19c0e104db95f78540982c64d78217cd9830d72.tar.xz | |
ath11k: Handle failure in qmi firmware ready
In some scenarios like firmware crashes during init time
and hardware gets restarted after qmi firmware ready event.
During restart, ath11k_core_qmi_firmware_ready() returns timeout.
But, this failure is not handled and ATH11K_FLAG_REGISTERED is set.
When hardware restart completed, firmware sends firmware ready event
again. Since ATH11K_FLAG_REGISTERED is already set, ath11k handles
this as core restart. Inits are not done because of previous timeout.
But ath11k_core_restart does deinit's which causes NULL pointer crash.
Fix this by handling failure from ath11k_core_qmi_firmware_ready().
Tested-on: QCN9074 hw1.0 PCI WLAN.HK.2.7.0.1-00881-QCAHKSWPL_SILICONZ-1
Signed-off-by: Seevalamuthu Mariappan <quic_seevalam@quicinc.com>
Signed-off-by: Kalle Valo <quic_kvalo@quicinc.com>
Link: https://lore.kernel.org/r/1645079195-13564-1-git-send-email-quic_seevalam@quicinc.com
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions