[PATCH v3] ath10k: Don't always treat modem stop events as crashes

Kalle Valo kvalo at codeaurora.org
Tue Oct 5 07:26:51 PDT 2021

Stephen Boyd <swboyd at chromium.org> wrote:

> When rebooting on sc7180 Trogdor devices I see the following crash from
> the wifi driver.
>  ath10k_snoc 18800000.wifi: firmware crashed! (guid 83493570-29a2-4e98-a83e-70048c47669c)
> This is because a modem stop event looks just like a firmware crash to
> the driver, the qmi connection is closed in both cases. Use the qcom ssr
> notifier block to stop treating the qmi connection close event as a
> firmware crash signal when the modem hasn't actually crashed. See
> ath10k_qmi_event_server_exit() for more details.
> This silences the crash message seen during every reboot.
> Fixes: 3f14b73c3843 ("ath10k: Enable MSA region dump support for WCN3990")
> Cc: Youghandhar Chintala <youghand at codeaurora.org>
> Cc: Abhishek Kumar <kuabhs at chromium.org>
> Cc: Steev Klimaszewski <steev at kali.org>
> Cc: Matthias Kaehlcke <mka at chromium.org>
> Cc: Rakesh Pillai <pillair at codeaurora.org>
> Signed-off-by: Stephen Boyd <swboyd at chromium.org>
> Reviewed-by: Rakesh Pillai <pillair at codeaurora.org>
> Tested-By: Youghandhar Chintala <youghand at codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo at codeaurora.org>

Patch applied to ath-next branch of ath.git, thanks.

747ff7d3d742 ath10k: Don't always treat modem stop events as crashes



More information about the ath10k mailing list