From: Rakesh Pillai <pillair@xxxxxxxxxxxxxx>
Currently in case of target hardware restart ,we just reconfig and
re-enable the security keys and enable the network queues to start
data traffic back from where it was interrupted.
Many ath10k wifi chipsets have sequence numbers for the data
packets assigned by firmware and the mac sequence number will
restart from zero after target hardware restart leading to mismatch
in the sequence number expected by the remote peer vs the sequence
number of the frame sent by the target firmware.
This mismatch in sequence number will cause out-of-order packets
on the remote peer and all the frames sent by the device are dropped
until we reach the sequence number which was sent before we restarted
the target hardware
In order to fix this, we trigger a disconnect in case of hardware
restart. After this there will be a fresh connection and thereby
avoiding the dropping of frames by remote peer.
The right fix would be to pull the entire data path into the host
which is not feasible or would need lots of complex/inefficient
datapath changes.
Rakesh Pillai (1):
ath10k: Set wiphy flag to trigger sta disconnect on hardware restart
Youghandhar Chintala (2):
cfg80211: Add wiphy flag to trigger STA disconnect after hardware
restart
mac80211: Add support to trigger sta disconnect on hardware restart
drivers/net/wireless/ath/ath10k/core.c | 15 +++++++++++++++
drivers/net/wireless/ath/ath10k/hw.h | 3 +++
drivers/net/wireless/ath/ath10k/mac.c | 3 +++
include/net/cfg80211.h | 4 ++++
net/mac80211/ieee80211_i.h | 3 +++
net/mac80211/mlme.c | 9 +++++++++
net/mac80211/util.c | 22 +++++++++++++++++++---
7 files changed, 56 insertions(+), 3 deletions(-)
--
2.7.4
