When SAP and GO home channels are in MCC in same band,
implement below requirement to avoid MCC:
1. SAP starts at first and GO starts later, then SAP will
force SCC to GO's home channel after GO starts up.
2. GO starts at first and SAP starts later, then SAP will
force SCC to GO's home channel during starting up.
3. SAP and GO SCC in same band, SAP changes channel to
the other channel in same band, GO will follow SAP and
move to SAP home channel.
4. SAP and GO SCC in same band, GO changes channel to the
other channel in same band, SAP will follow GO and move
to GO home channel.
And all the force SCC cases, if the target channel of force
SCC is not supported by the SAP or GO, then driver will
select other band's channel for the interface.
Change-Id: I7b24f3a972a401fd144a0c81dc19bd48ba224d85
CRs-Fixed: 3176087
Currently, wakelock is only taken during initial connection if
pairwise key installation is pending and not during roaming. This
may lead to EAPOL delay/timeout during roaming as runtime pm and
suspend is allowed during roaming. To fix this issue, acquire
wakelock if key installation is pending during roaming.
This change also refactors the code and release the wakelock in
wma_remove_peer if EAPOL fails during initial connection or roaming.
Change-Id: Id4cac30b3c383ca3d3e963571846f8a30eaa1006
CRs-Fixed: 3189799
In case if HW doesn't support 160 Mhz BW, driver
doesn't update 160 Mhz capability in WIPHY and
even in such case if Userspace configures ACS
BW as 160 Mhz in hostapd, Driver selects this
bw for acs without checking whether HW support
this BW. This leads to mismatch between ACS BW
and supported Wiphy BW and ultimately leading
to SAP start failure for 160 Mhz for 5 ghz and
6 ghz band.
So, Update ACS BW with HW Supported BW such
that if hw doesn't support 160 Mhz bw then acs
bw 160 Mhz shouldn't be selected.
As in wiphy we won't enable 160 Mhz capability.
Change-Id: I195b0e6bd0ce7640f136077ed9042c6e15088143
CRs-Fixed: 3170528
EAPOL TX message enters the driver via NL and not
through the ndo_select_queue. Hence skb->queue_mapping
value is not set.
This fix will set the correct value to queue_mapping
for EAPOL packets. The EAPOL TX packets will hence be
marked correctly in the wlan_hdd_mark_critical_pkt()
and then logged.
Change-Id: I97018c4e8b44c55f9924c1465b41fcfdbc50406c
CRs-Fixed: 3190128
6 GHz STA profile contains HT and VHT capabilties in association
request when STA tries to associate 2.4 GHz + 6Ghz MLO connection.
Removed HT and VHT capability population from MLO IE preparation
when MLO connection is 2.4 GHz + 6 GHz.
Change-Id: Ie21723fb1f9c81404015a7de4f787447acbf9e90
CRs-Fixed: 3200099
EasyMesh agent fails to update the phymode requested by controller.
EasyMesh controller sends the channel selection request package to notify
EasyMesh agent to change phymode and channel. EasyMesh agent should change
them accordingly.
Update the phymode of the SAP, then restart the SAP.
Change-Id: Iab881b0bfbd1764072b48d426610adc8967111cd
CRs-Fixed: 3181195
Previous linkspeed only enabled for P2P mode,
and here extend for STA/SAP mode per request.
Change-Id: I0976ee2e4b064b74cc2532a310f20e0ef1b0e7f6
CRs-Fixed: 3205568
There is only 1 global var to save EHT cap in psoc cfg for both 2 GHz and
5 GHz band, it is propagated to vdev/pe session/frames without revising by
band, so EHT cap of 2 GHz and 5 GHz are same, EHT cap of assoc link and
partner link are same, so no EHT cap in ML-Link Info(per STA Profile) in
assoc request while connecting to EHT MLO AP.
To fix it, revise EHT cap when band is selected, get EHT cap by band when
assemble assoc req MLO link per sta profile, get correct 2 GHz cap by
checking supported bands when get MAC/PHY cap from firmware, copy supported
MCS set from firmware to EHT cap of 2 GHz and 5 GHz too.
Change-Id: Ie97e71ee141f023248fb49f9977e7345e21003f6
CRs-Fixed: 3200199
When verifying WNM BSS transition function, it's possible to
ask peer STA to transition across multiple band. Some vendor
BTM implementation is needed to check country IE to get all
supported band channel info. Without full channel list in
country IE, it cannot make a transition across multiple band.
To solve the interop issue, let country IE take all supported
band channel info when the specific vendor OUI is detected in
association request.
Change-Id: I78dd4b88937277b54a7da4d72d8a94706965e9a6
CRs-Fixed: 3196957
This reverts commit I9701830d. Host needs to honor the ll stats
command in disconnected state also.
CRs-Fixed: 3197453
Change-Id: I32db288cf070bba21023536c0d9e933835f26c53
Currently driver checks TX flag only for authentication
frames. This causes wrong tag for the frames.
Check TX flag for Deauth/Disassoc & authentication frames
also.
Change-Id: Id499bc1978ee72bac2435be165b31d0db49ce9d8
CRs-Fixed: 3203858
bss_transition bit is not set in extend capability IE of reassoc request
frame, while it is set in extend capability IE of assoc request frame.
The way to populate extend capability IE of reassoc request should be
the same as we do for assoc reqest frame.
Change-Id: I22a56c7c9f8926d88d0da7d0445ff5f6a8249320
CRs-Fixed: 3200723
Currently in case of SBS, if two connections are on one mac and
one connection is on another mac new connection can come up only
on 5 GHZ Low/5 GHZ high based on the mac that can support new connection.
But weightage of all 5 GHZ low/high channel is marked same instead of
prioritizing SCC channel.
Fix is to provide more weightage to 5 GHZ low/high SCC channel than
rest 5 GHZ low/high channels.
Also Optimize few logs.
Change-Id: I4153b209e6a74fe79081116baecaae78be5b632b
CRs-Fixed: 3204041
Add API policy_mgr_check_force_scc_three_connection
to select force SCC channel for 3 vifs existing case in
policy_mgr_check_scc_sbs_channel.
Change-Id: Ie092c15164939306a8723038f6418ab722314f7c
CRs-Fixed: 3178588
Send connected links bitmap to FW via a command:
WMI_REQUEST_STATS_EXT_CMDID in case of MLO connection.
Host receives partner link stats via WMI_STATS_EXT_EVENTID
event and sends information of partner links to upper layer.
Change-Id: Iddd617f1acb5e29e4ba6d52baae0b421c4886063
CRs-Fixed: 3148451
Driver reports unsafe channel to the upper layer although
channel is unsafe.
Ignore the channels which are unsafe after examination
of whether channel is safe or not by the use of
policy_mgr_is_safe_channel() and report safe channel
to upper layer
Change-Id: Idfe741d19b8641814888938eab37a1daa83b7dd9
CRs-Fixed: 3197317
Add logic to disable a link vdev if concurrency doesn't allow it.
Send mlo_force_link_inactive in peer assoc for this and add
it in deleted table on connection complete.
Also disable the link if roam sync indication indicate
that link is disabled.
Change-Id: Ib0615308a669a5fd9d2b8ef6f8ab3f50953f658d
CRs-Fixed: 3192728
Call enable/disable link APIs from connect/disconnect/roam etc.
Cleanup policy_mgr_handle_sap_mlo_sta_concurrency and
policy_mgr_handle_sap_plus_ml_sta_connect API as
policy_mgr_handle_sap_cli_go_ml_sta_up_csa and
policy_mgr_re_enable_ml_sta_on_p2p_sap_down will take care of
ML STA + SAP/P2P cases.
Also optimize policy_mgr_handle_ml_sta_link_concurrency to consider
only ML STA+STA cases and called from connect/disconnect/roam etc.
Change-Id: Ib8b9b2a490832ea5cbe1d86e58009e1437b331b9
CRs-Fixed: 3189685
Add logic to enable and disable number of STA ML link, on vdev UP
and DOWN, if any link is causing MCC with exiting
SAP/P2P and SAP/P2P with traffic type as low latency or high tput.
Change-Id: Id599acf5a07042328917b5e15f077d2decc0ad5f
CRs-Fixed: 3189304
assoc_ind->ch_width is updated in function lim_fill_assoc_ind_he_bw_info,
but assoc_ind->chan_info.rate_flags is not updated. It causes BW out of sync
between these two variables.
To resolve this issue, update assoc_ind->chan_info.rate_flags accordingly
at same time.
Change-Id: Ifab85d7ced977f3a3f032853f37dfcdeadb8db26
CRs-Fixed: 3196799
For setting tspec uapsd mask per session
in sme_qos_del_ts_req(), Don't use tsinfo
from pMsg as before setting tspec uapsd
mask, eWNI_SME_DELTS_REQ msg is posted
to lim and as part of processing this
msg, pMsg is mem_freed.
This will cause use after free error so
as fix, fill the pMsg tspec to a local
variable before posting msg to lim and
pass it to
sme_set_tspec_uapsd_mask_per_session()
Change-Id: I9bded004ca3e9d612811c7533e655be1e2cdff42
CRs-Fixed: 3201541
Add disabled links table and APIs to move and remove
vdevs from disabled links table.
Change-Id: I610bbd10e387a4bcd3a5d5c88c3dba5698878441
CRs-Fixed: 3181474
Add PCL handling for ML STA + P2P + P2P concurrencies,
based on current hw mode (SBS/DBS/SMM).
Change-Id: I337b12a0c03ab89968572056f27f47a6b9392803
CRs-Fixed: 3177305
In new framework the 6 GHz preferred SAP ACS config file will
contain 5 GHz channels, to avoid 6 GHz non-PSC being set to
MAX weight value and 5 GHz channels selected easily, here set
normalize_acs_weight to 90 for non-PSC channel of 6 GHz, 40
for 2 GHz and 5 GHz channels.
Change-Id: I5e89339d0fd4e3c190dd2ead1ec87d12ff197691
CRs-Fixed: 3186587
If normalize_acs_weight INI setting covers the DFS channel,
the existing DFS channel weight factor will be override.
Fix it by using the minimal weight factor for both setting.
Change-Id: Ie0fa3371bd99ee8d50c7abc81ddc8cd0eb84f9aa
CRs-Fixed: 3196688
To make the active connections number configurable, based on
host configuration of INI gMaxConcurrentActiveSessions
host sets the num_max_active_vdevs in WMI init command to notify
the FW the number of active connections host expects to support.
FW will report the actual supported number in wmi ready event.
Policy mgr will record the FW supported number if FW number is
smaller than host requested.
Change-Id: I454c0cdde6be1e8a627f8fff08b6c7b2141b00f6
CRs-Fixed: 3183006
If force SCC enabled, user trigger SAP CSA and target channel
doesn't cause MCC with existing STA/CLI. Then overide strict flag to
true, so that driver can skip the overlap interference check and
allow the CSA go through. This is to allow SAP/GO force SCC in
same band.
Change-Id: I7844f7329b922456594cad1402a0d2ac0d0927c5
CRs-Fixed: 3178725
Add support for new ini param RoamCommon_MinRoamDelta. This param
is similar to the existing min_roam_score_delta param but units
change
Change-Id: If04ff2344a2651e7d8d71c92f05dfebc229f9fe1
CRs-Fixed: 3015930
Add support for new ini param RoamIdle_InactiveTime. This param
is similar to the existing idle_roam_inactive_time but unit
change
Change-Id: I857107a6d0e39f373e39d4fb9b762e7cf4c4a9e4
CRs-Fixed: 3015993
hdd_wds_replace_peer_mac will modify the input mac addr, the destination
mac addr of skb is modified once we pass skb->data as a pointer to the
hdd_wds_replace_peer_mac.
Use a local variable to get mac addr in skb, then hdd_wds_replace_peer_mac
will not modify mac addr in skb.
Change-Id: Ie0f6f4365b8558a451fa8434832f14aebd56172b
CRs-Fixed: 3196225
Keep SCC channels in the PCL list, if SCC is allowed on those
frequencies.Do not remove these frequencies, if the
mandatory channel list doesn't have the SCC frequencies.
Also, whenever the user configured frequency of the SAP is
different following a STA disconnect, switch it back to the
home channel.
Change-Id: Ia5fe8943136791084de02a2d3a8ff250008978be
CRs-Fixed: 3196278
