The operation class field in RNR is using global operation class.
When getting frequency from RNR IE, we should search operation
class in global operation class table.
Change-Id: Ie9ff62e1d98cb10debfcff734e28ffaecf14e321
CRs-Fixed: 3031211
CSA IE TX isn't offload to FW, the count of Beacon with CSA IE
actually DUT sent exceeds the required. So, this change clear CSA IE
and update Beacon frame.
Change-Id: Ib433b9d2877b332365a4cfdf1a6bca56d6194672
CRs-Fixed: 3008327
In order to support four STA default interfaces
to be created and up after driver loaded, it
requires setting bmiss_offload_max_vdev=4 to
Hastings fw. So export this variable to be
configurable and can be modified if in need.
Change-Id: I25db5dd72de7d45c6be682891abba711edaf20dd
CRs-Fixed: 3030148
For STA connection in HE 160, HE160 MCS is validated
during the session creation. If the HE160 is invalid,
the connection falls back to 80MHz. But, this check needs
to be bypassed for SAP, because during session creation SAP
will not have the peer capability, so the HE160 MCS validation
needs to be bypassed.
Change-Id: I3bbb2f35c40a123b5d05a94038970a0e7e43ac60
CRs-Fixed: 3025102
When the connect request is pending on MLME and NB disconnect comes,
driver will wait for previous connect finish to process the disconnect
request. This delay the disconnect and may cause framework ANR.
Add code to fire the timeout event of active timers in various MLME
state. This will abort the connect request and get disconnect done fast.
Change-Id: I19cc03108c966c8f1efc0a554dfc59123dfe37f1
CRs-Fixed: 3026311
Currently the PS config received from kernel/userspace is set
to mac_ctx globally. This causes PS config set for one vdev to
override on the other vdev.
To avoid this, set the PS config per vdev.
Change-Id: I6a2e2a9d8fb67b94d9d5f1d4164077990bdaf4a5
CRs-Fixed: 3007060
In the 2.4G 1x1 + 5G 2x2 Hastings specific case,
host will receive below HE MCS info:
1. hw mode id[0], phy id[0]
he_supp_mcs_2G=0x0
he_supp_mcs_5G=0xfffefffa
2. hw_mode_id=1 phy_id=0
he_supp_mcs_2G=0x0
he_supp_mcs_5G=0xfffefffa
3. hw_mode_id=1 phy_id=1
he_supp_mcs_2G=0xfffe
he_supp_mcs_5G=0x0
But in the wma_update_target_ext_he_cap, it always
updates the last mcs=0xfffe info into he_cap,
which will be used in the HE capability of beacon
or probe response frame whatever it running on
2.4G or 5G and it is not right.
So add this fix to update the MCS separately according
to the current operating channel.
Change-Id: I277aa708ae7e13917cf2068f01b05d3864ad7618
CRs-Fixed: 2992253
Optimize STA disconnect handling In LIM, by improving logging
and seperating logic from SAP's peer disconnect handling.
Change-Id: Iad2cc1ac0b5dc3e5ce7294e410d6d8040934ea0d
CRs-Fixed: 3026218
Some AP indicates it support 40M in HTInfo, while not support 40M in
HTCaps, so need intersect HTInfo and HTCaps.
Change-Id: I496b62f50a2e1e19aeef7e77535d0479f31bba44
CRs-Fixed: 3025951
