diff options
| author | Wen Gong <[email protected]> | 2019-11-27 03:19:24 +0000 |
|---|---|---|
| committer | Kalle Valo <[email protected]> | 2019-11-29 09:43:12 +0200 |
| commit | 382e51c139ef9d0b8e65ff5c249771f864b411fd (patch) | |
| tree | 1a0630e80203d0470e396a926457f1417cac0602 /tools/perf/scripts/python/syscall-counts-by-pid.py | |
| parent | 376a30c7c9a05382d2cad09e9ff9b2998d0d53c3 (diff) | |
ath10k: set WMI_PEER_AUTHORIZE after a firmware crash
After the firmware crashes ath10k recovers via ieee80211_reconfig(),
which eventually leads to firmware configuration and including the
encryption keys. However, because there is no new auth/assoc and
4-way-handshake, and firmware set the authorize flag after
4-way-handshake, so the authorize flag in firmware is not set in
firmware without 4-way-handshake. This will lead to a failure of data
transmission after recovery done when using encrypted connections like
WPA-PSK. Set authorize flag after installing keys to firmware will fix
the issue.
This was noticed by testing firmware crashing using simulate_fw_crash
debugfs file.
Tested with QCA6174 SDIO with firmware WLAN.RMH.4.4.1-00007-QCARMSWP-1.
Signed-off-by: Wen Gong <[email protected]>
Signed-off-by: Kalle Valo <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts-by-pid.py')
0 files changed, 0 insertions, 0 deletions