In case STA is in connected state, and the PMF SAP receive Assoc
request from the STA, the assoc request is silently dropped.
Instead the SAP should send assoc resp with comeback time and
start SA query.
Fix it by not dropping the duplicate assoc request frame for PMF
capable STA.
Change-Id: I812fb40541c93e7cac470b9154217844eac8a86d
CRs-Fixed: 2017250
Inform the bss using the new API cfg80211_inform_bss_frame_data() which
also has the ability to inform the timestamp when the frame has
been received.
If the support is not present in the kernel fallback to the legacy
inform bss.
Change-Id: Iaa512248a5e56d77cff39da562e0c9ee4eaeeefd
CRs-Fixed: 1082423
Check the FW capabilities to enable VHT160MHz support.
Disable 160MHz by default in the configuration.
Change-Id: Ia6985d9f7c55a070dbb47faf95cd409201037e0c
CRs-Fixed: 2004245
Add new diag events for the wlan disconnection these
events will be used to inform the wlan disconnection scenario.
Change-Id: I6bdddb2d3f45deca2dc92a94e2abf59f46d7c38f
CRs-Fixed: 1108380
Add QCN IE with version attribute to probe request and assoc/reassoc
request. Add support to detect the QCN IE in beacon, probe response and
assoc/reassoc response.
Change-Id: Ieac62517b09fb5bcd2a1709a352035f422c9ce63
CRs-Fixed: 1116843
Currently driver does not wait for peer del response from firmware,
but posts del sta response indication to SME immediately. This
can cause an assert in firmware if driver receives add sta
immediately before even del sta response from firmware. Add
changes to wait for peer del response from firmware to fix
this.
Change-Id: I16a84256f4a1ed971c17eb3139faac5622eadda4
CRs-Fixed: 2008940
wlan-cld3.driver.lnx.1.1-dev to wlan-cld3.driver.lnx.2.0-dev propagation
As per the current code, upon receiving the disassociation frame
AP, DUT-STA disconnects from the AP link but not tearing down the
TDLS link with peer by sending deauth with reason code 3.So when
AP comes up again TDLS link is not establishing between the
peers.
Fix is to delete all connected TDLS peers upon receiving
disassociation framefrom AP.
Change-Id: I8daa61cb1901441e5fae7d161c9f943d67e13c56
CRs-Fixed: 1081264
qcacld-2.0 to qcacld-3.0 propagation
In the current code, when STA receives CSA IE then host look and
operate on extended channel switch element eventhough our own
channel-bonding state is not enabled. This causes setting up of
secondary subband and state in new channel during CSA eventhough
the secondary channel offset is set to zero in CSA beacon.
Fix is to set the Secondary Channel Offset if our own channel
bonding state is enabled.
Change-Id: I82ca9737f49937176801bc4cbbdd3e2fb77d4749
CRs-Fixed: 1080260
Firmware may send STA kickout event even during association. This
change the limSmeState to eLIM_SME_WT_DEAUTH_STATE from
eLIM_SME_WT_ASSOC_STATE. Due to this assoc confirm is not processed
and HDD remains in connecting state and thus all subsequent scans
fails.
Fix this by processing STA kickout event only in
eLIM_MLM_LINK_ESTABLISHED_STATE
Change-Id: I75b4814aade80ca74ef9aef67ecea99a3bc15148
CRs-Fixed: 2012727
