summaryrefslogtreecommitdiffstats
path: root/include/net/mac80211.h
diff options
context:
space:
mode:
authorEliad Peller <eliad@wizery.com>2016-02-14 13:56:36 +0200
committerJohannes Berg <johannes.berg@intel.com>2016-02-24 09:04:39 +0100
commit1ad4f639cc3e09d6c8402a0fcc592e2391683e31 (patch)
tree3f87ad51286107613ff963ec5ede138bfaafa8f4 /include/net/mac80211.h
parentf8079d43cf0f1f0171606e75fcef6fe17bb183f2 (diff)
downloadlinux-1ad4f639cc3e09d6c8402a0fcc592e2391683e31.tar.gz
linux-1ad4f639cc3e09d6c8402a0fcc592e2391683e31.tar.bz2
linux-1ad4f639cc3e09d6c8402a0fcc592e2391683e31.zip
iwlwifi: mvm: move TX PN assignment for TKIP to the driver
If protocol offloading is configured, the fw might generate some frames (e.g. arp response) on its own during d3/d0i3. On d3/d0i3 exit the driver queries the updated PN (if relevant), and updates its keys (for the d0i3 case, this is done by iwl_mvm_d0i3_exit_work(), which is scheduled on d0i3 exit) While in d0i3, iwlmvm defers tx frames until d0i3 exit, and then continues their processing. This is problematic with TKIP, since the frame's PN has already been set at this stage (in contrast to CCMP, where the PN is being set only later on), so both the frame's PN and the upcoming PN update (from d0i3 exit work) might be wrong. Fix it by moving the TX PN assignment (for TKIP) to the driver, similarly to CCMP. Signed-off-by: Eliad Peller <eliadx.peller@intel.com> Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'include/net/mac80211.h')
0 files changed, 0 insertions, 0 deletions