mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-24 13:44:26 -04:00
qcacld-3.0: Don't modify BTM capability in the extended capabilities
Currently the host driver checks if the BTM offload is enabled via ini configuration and sets the BTM enabled bit of the extended capabilities if BTM offload is enabled. The supplicant decides if BTM is needed to be enabled or disabled based on the PMF capability of the AP, since the STA is MBO certified. When driver sets the BTM capability based on the btm_offload ini, even if the AP supports MBO and doesn't advertise PMF, BTM is honored by the MBO certified STA. This violates the MBO spec that PMF is mandatory for MBO. So with the BTM capability controlled by userspace, the BTM capability will be advertised to MBO AP only if PMF is advertised as required for that AP. Don't modify the BTM capability, and advertise it as it is provided by the userspace. Firmware will drop the packet if BTM capability is not advertised during initial connection. Change-Id: I55b4e46a44011ce7a1982244df17ea32632f7ff3 CRs-Fixed: 2568311
This commit is contained in:
parent
f47fbb3664
commit
f37e5e7637
1 changed files with 0 additions and 3 deletions
|
|
@ -1196,9 +1196,6 @@ populate_dot11f_ext_cap(struct mac_context *mac,
|
|||
if (pe_session && pe_session->is_mbssid_enabled)
|
||||
p_ext_cap->multi_bssid = 1;
|
||||
|
||||
if (mac->mlme_cfg->btm.btm_offload_config & BTM_OFFLOAD_ENABLED_MASK)
|
||||
p_ext_cap->bss_transition = 1;
|
||||
|
||||
/* Need to calculate the num_bytes based on bits set */
|
||||
if (pDot11f->present)
|
||||
pDot11f->num_bytes = lim_compute_ext_cap_ie_length(pDot11f);
|
||||
|
|
|
|||
Loading…
Reference in a new issue