aboutsummaryrefslogtreecommitdiffstats
path: root/net/mac80211/rc80211_minstrel_ht.h
diff options
context:
space:
mode:
authorManikanta Pubbisetty <mpubbise@codeaurora.org>2018-03-28 18:34:19 +0530
committerJohannes Berg <johannes.berg@intel.com>2018-03-29 11:35:22 +0200
commitdb3bdcb9c3ffc628c5284d7ed03a704295ba1214 (patch)
tree29260761f4478e8cb841fa9a2b841d57615afe74 /net/mac80211/rc80211_minstrel_ht.h
parentcfg80211: Add API to allow querying regdb for wmm_rule (diff)
downloadlinux-dev-db3bdcb9c3ffc628c5284d7ed03a704295ba1214.tar.xz
linux-dev-db3bdcb9c3ffc628c5284d7ed03a704295ba1214.zip
mac80211: allow AP_VLAN operation on crypto controlled devices
In the current implementation, mac80211 advertises the support of AP_VLANs based on the driver's support for AP mode; it also blocks encrypted AP_VLAN operation on devices advertising SW_CRYPTO_CONTROL. The implementation seems weird in it's current form and could be often confusing, this is because there can be drivers advertising both SW_CRYPTO_CONTROL and AP mode support (ex: ath10k) in which case AP_VLAN will still be supported but only in open BSS and not in secured BSS. When SW_CRYPTO_CONTROL is enabled, it makes more sense if the decision to support AP_VLANs is left to the driver. Mac80211 can then allow AP_VLAN operations depending on the driver support. Signed-off-by: Manikanta Pubbisetty <mpubbise@codeaurora.org> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'net/mac80211/rc80211_minstrel_ht.h')
0 files changed, 0 insertions, 0 deletions