diff options
| author | Manikanta Pubbisetty <[email protected]> | 2022-06-02 17:59:29 +0530 |
|---|---|---|
| committer | Kalle Valo <[email protected]> | 2022-06-06 17:09:20 +0300 |
| commit | 0ab52b2bd7be8fd49c8ade7703c1faa15359c6c5 (patch) | |
| tree | f3e20411fcb75ba4a486de856a3d872318a4a51d /tools/perf/scripts/python/event_analyzing_sample.py | |
| parent | 9331f7d3c54a263bede5055e106e40b28d0bd937 (diff) | |
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 <[email protected]>
Signed-off-by: Kalle Valo <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions