ath11k: Avoid REO CMD failed prints during firmware recovery
authorManikanta Pubbisetty <quic_mpubbise@quicinc.com>
Thu, 2 Jun 2022 12:29:29 +0000 (17:59 +0530)
committerKalle Valo <quic_kvalo@quicinc.com>
Mon, 6 Jun 2022 14:09:20 +0000 (17:09 +0300)
commit0ab52b2bd7be8fd49c8ade7703c1faa15359c6c5
treef3e20411fcb75ba4a486de856a3d872318a4a51d
parent9331f7d3c54a263bede5055e106e40b28d0bd937
ath11k: Avoid REO CMD failed prints during firmware recovery

Currently when firmware recovery is in progress, we do not queue REO
commands to the firmware, instead -ESHUTDOWN will be returned to the
caller leading to a failure print on the console. The REO command in
the problem scenario is sent for all tids of a peer in which case we
will have 16 failure prints on the console for a single peer. For an
AP usecase, this count would be even higher in a worst case scenario.
Since these commands are bound to fail during firmware recovery, it
is better to avoid printing these failures and thereby avoid message
flooding on the console.

Tested-on: WCN6750 hw1.0 AHB WLAN.MSL.1.0.1-00887-QCAMSLSWPLZ-1

Fixes: 8ee8d38ca472 ("ath11k: Fix crash during firmware recovery on reo cmd ring access")
Signed-off-by: Manikanta Pubbisetty <quic_mpubbise@quicinc.com>
Signed-off-by: Kalle Valo <quic_kvalo@quicinc.com>
Link: https://lore.kernel.org/r/20220602122929.18896-1-quic_mpubbise@quicinc.com
drivers/net/wireless/ath/ath11k/dp_rx.c