Currently probe request is sent every 200ms during join timeout
this can lead to 16+ probe req, send during join time.
Change logic to send max 5 probe req during join time,
if candidate freq can lead to MCC concurrency scenario.
Change-Id: I7956771e2cf6724754f59c6db5b07fb45426ae41
CRs-Fixed: 3338329
In 11be capable configuration, for connection attempt
to MLO AP from non-MLO type vdev, downgrade to 11ax
mode association for that vdev.
User can still connect in ML mode from MLO type vdev.
Change-Id: I1e7cf940a778a20f2f4d5d24283ffb6aae52781b
CRs-Fixed: 3312163
In policy_mgr_get_index_for_ml_sta_sap_hwmode_sbs,
if SBS supported, at least one share type should be
supported.
Fix the missing check of Low share SBS.
Change-Id: I9ab848bab9ae8eb5c9d4bb85022b83be92e4c1e9
CRs-Fixed: 3338956
In SBS disabled, STA connects to MLO AP, then start P2P GO on 2.4 GHz.
The non SBS 3rd connection PCL table doesn't support such combination
and P2P GO start is failed.
Fix by add P2P GC/GO valid PCL type for PM_STA_STA_DBS_2x2
Change-Id: I8d36a11ca0005a25d17187100124e355fcb945ca
CRs-Fixed: 3334208
Kernel doc mismatch in policy_mgr_are_sbs_chan(). Correct it
by adding proper argument.
Change-Id: Ic72659df96bac1f98323ec7a9d339d0a975434a0
CRs-Fixed: 3336165
Policy manager restricts concurrent ML SAP and ML STA
operation in existing rules.
Allow atmost one ML SAP to exist and disallow any secondary
ML SAP start BSS.
Allow ML STA even if ML SAP is present, as only one ML SAP
is allowed, remove the code check for is ML SAP while checking
concurrency rules for ML STA.
Change-Id: Icced604c1685eaf00452b240d816fdd8bc2a97d2
CRs-Fixed: 3331402
If ml sta is not "connected" state, no need to do link state handling.
After disconnected, target will clear the force active/inactive state
and host will remove the connection entry finally.
After roaming done, active/inactive will be re-calculated.
Change-Id: Ic9ba3e3ef704b3dcdd8185e9b0864a9cbac000c7
CRs-Fixed: 3322063
With 11be mlo, the number of open station interfaces is 3.
Modify the check in policy manager api for the same.
CRs-Fixed: 3320739
Change-Id: I89166ebdf1559cde6f77f5a5c535e5f2e81eefc5
Currently, roaming is disabled with requestor "RSO_CONNECT_START"
on the STA when concurrent P2P-client is connected .
It's re-enabled once the P2P-client is disconnected but with
requestor RSO_INVALID_REQUESTOR. Roaming module still doesn't
re-enable roaming as it expects roam-enable command from the
requestors(i.e. RSO_CONNECT_START in this case) which disabled
roaming.
Pass right requestor to re-enable roaming.
Change-Id: Icb3deeed788ca248391b4b84288229aea2bdb8c2
CRs-Fixed: 3330219
For MLO STA+SAP case, mlo link maybe in inactive state after
connected and the hw mode maybe not updated, check MCC/SCC by
policy_mgr_are_2_freq_on_same_mac may not match MCC/SCC state
after the link is activated by target later. So to check frequency
match or not to decide SAP do force SCC or not if MLO STA 2 links
are present.
Change-Id: I614e6879cf4f9614b979fc3c78f87b76fc6c7c16
CRs-Fixed: 3313043
If existing STA+STA is MLO STA, the current HW mode is not
reliable because the STA link maybe inactive. HW mode may
change if MLO STA becomes active.
Add special handling to this case by checking MAC frequency
range to decide DBS or SBS.
Change-Id: I4d3728965d2f687805535abb0716bb1b58e1c51d
CRs-Fixed: 3328517
In concurrency case: GO on 5180 MHz, SAP on 5765 MHz,
MLO STA vdev 0 5180 MHz, MLO STA vdev 1 2462 MHz.
When the MLO STA is up and driver does force SCC on
SAP, the get PCL is failed because the GO vdev,
MLO STA vdev 0 and vdev 1 are all non-SBS channels
between each other. Driver doesn't handle the case in
policy_mgr_get_index_for_ml_sta_sap_sbs if current
hw mode is SBS. This case can happen the mlo sta link
vdev is inactive after get connected.
To fix it add new API:
policy_mgr_get_index_for_ml_sta_sap_hwmode_sbs to
handle it. It will return the correct PCL index
to avoid 3 home channels on same mac.
Change-Id: Ia16f8a391b34fc15287a93590b2c119d58250e20
CRs-Fixed: 3326358
Don't allow ML links to form MCC, if second
ML link is trying to form MCC then send disable
to FW and FW will decide which link to be disabled
to avoid MCC. Similarly if any SAP/P2P link disables
then ML STA link shouldn't enable back if it can cause
MCC with existing ML link.
Change-Id: I9bd8e257ad3fc3ee54d9e9d79c66962469b0b827
CRs-Fixed: 3313944
For eMLSR mode, the lower 27 bits of hw_mode_config_type
are HW mode and higher 5 bits are MLO Cap flag.
To update MAC frequency info correctly, get hw mode type
for eMLSR by macro WMI_BECAP_PHY_GET_HW_MODE_CFG().
Change-Id: I18a0afb26985b6ccda091fa1564713af0260353f
CRs-Fixed: 3314401
With MACRO FEATURE_WLAN_CH_AVOID_EXT enabled,
"restriction_mask" can only be checked if
coex_unsafe_chan_nb_user_prefer = 1. If the INI
coex_unsafe_chan_nb_user_prefer = 0, do not need to check
"restriction_mask". It will remain uninitialized 0.
Change-Id: If7bd1223ee3779b72fadb40e622f682db03f4ea5
CRs-Fixed: 3287634
Currently CH_WIDTH_MAX is set as default BW when sap do restart,
then apply some checking rules to get the final BW. It's possible
the final BW is greater than sap original BW. But a greater BW
isn't expected in some use cases where greater BW may introduce
some unexpected issues.
Add INI to configure sap original BW as default BW when do sap
restart as required.
Change-Id: Ie274a3eea73c2af9424a8b9ce21bee34eeaaef2e
CRs-Fixed: 3315486
Add check for QDF_MCC_TO_SCC_SWITCH_WITH_FAVORITE_CHANNEL while
getting the sap mandatory frequency.
Change-Id: Ia1dfdfb0818ed94620295e3f4046fbe16b5a92d8
CRs-Fixed: 3301096
As part upgrading legacy APIs with 6 GHz power APIs
Replace all occurrences of
wlan_reg_is_passive_or_disable_for_freq API with new API
wlan_reg_is_passive_or_disable_for_pwrmode.
Change-Id: If8429146e3e4e4cb25505de9855671dca2eb6474
CRs-Fixed: 3306631
Check for 6 GHz channel for SCC was not there due to which,
6 GHz + 5 GHz(DFS) MCC was happening even if we are forcing SCC.
Change-Id: Iac02b1990ffa91a5b0688d6976bc38cbbd10acfb
CRs-Fixed: 3301115
If there is existing interface STA/GC/SAP/GO/ML STA and
low latency SAP tries to come then allow only if below
condition satisfies
1. DBS hw_mode: Allow if existing interface is on 2.4 GHz
channel otherwise reject.
2. SBS hw_mode: Allow if existing interface channel and low
latency SAP channel are mutually exclusive.
Change-Id: I67a883b89f63fa581379cb303da6c11b43e65912
CRs-Fixed: 3296640
SAP MCC with ML STA link is not preferred since SAP is only
allowed off channel for max 32 ms.
If All ML STA are 5/6 GHz band, force SCC will not happen
for 2 GHz only SAP. Inactive one link if both ML STA are on non
2 GHz band.
Change-Id: I3450a0e66e583320cb91cd549317a197e5d1e039
CRs-Fixed: 3307863
In hw mode change offload case, frequency of the connections
in table pm_conc_connection_list may be updated later than the
mac frequency info which is updated when processing hw mode
transition event, then the current concurrency combination
dump here which is inferred from mac frequency info and
pm_conc_connection_list may be wrong.
To avoid confusion, replace concurrency combination dump with
current connection status dump when processing hw mode
transition event.
Change-Id: I0d8db410b3db3aa4b35c27f227bc68f5852a86d3
CRs-Fixed: 3315452
Add new entry in the enum qca_conn_diag_log_event_type in
order to support EAPOL start packet.
Change-Id: I540ef257ee9425eef016302648844ebf01647372
CRs-Fixed: 3314689
Add a support to check if low latency SAP is present on 5 GHz
channel then do not allow SAP/GO to come up on 5 GHz for
both gaming and lossless audio profile.
Change-Id: Ibb9e3365522beec541f70c6c45b8cb68405fd3bc
CRs-Fixed: 3294748
Add a support to check if low latency SAP is present on 5 GHz
channel then do not allow STA/GC to connect on 5 GHz for
both gaming and lossless audio profile.
Change-Id: I8e1c62dfea3c27306e338392448f5cc6eed912aa
CRs-Fixed: 3302763
Low latency SAP is supported on DBS and SBS hw and it can come
up on below two profile
a. Gaming
b. Lossless Audio
DBS: Allow only 2.4 GHz channel for both gaming and lossless
audio profile
SBS: Allow non low latency SAP 5 GHz channel which are mutually
exclusive for both gaming and lossless audio profile.
Check whether low latency sap is present or not. If it's present
then get the frequency to validate the concurrency with other
interface.
Change-Id: I39715a01e63de612448d4d0f230e6ccb71b76b15
CRs-Fixed: 3294596
Add INI g11be_oui_allow_list to config 802.11be AP oui which
is allowed to get connected in 802.11be mode.
If the INI is empty, all the ap are allowed to get connected
in 802.11be mode. If INI is set to "ffffff 00 01", then STA
is not allowed to connect to any AP in 802.11be mode.
Change-Id: I98e545ba909c1746237a20c365f8297f16fe666f
CRs-Fixed: 3304021
Add below two enhancements for SAP
1. Spatial Reuse enabled in single MAC concurrency
2. Set bit HESIGA_Spatial_reuse_value15_allowed in SRP IE
Change-Id: Id2d3d04ae1b3b9a2e6d84f30749b577bc7b79061
CRs-Fixed: 3305447
Currently the AKM information is sent as uint16_t variable
this leads to truncation of 1byte in connecting event of
advanced connectivity logging.
Update the AKM data type from uint16_t to uint32_t.
Change-Id: Ibe359636cb32b66ed99ee8ccb8ce33299908325b
CRs-Fixed: 3307515
Replace all occurrences of
wlan_reg_get_channel_state_for_freq with
wlan_reg_get_channel_state_for_pwrmode and use extra
parameter as REG_CURRENT_PWR_MODE.
Change-Id: I7f7e4e700091918eeebc87ccbbc85ececdd9bf52
CRs-Fixed: 3145011
As part of upgrading legacy code
with 6 GHz power APIs, replace
all ocurrances of
wlan_reg_is_disable_for_freq with
wlan_reg_is_disable_for_pwrmode.
Change-Id: Id18e48e27eb118945d56205797882874eb552153
CRs-Fixed: 3145764
Add API policy_mgr_is_mlo_sta_disconnected to check all STA
in mlo dev are disconnected. If any link is associated
the API will return false.
Change-Id: I2845e81b25b4dabe5cd52e80d230979ce44e9994
CRs-Fixed: 3302791
Return success instead of not supported when the underlying hardware
is not supporting SBS
Change-Id: I3bb890ca2e8f096a918e2e718d44980ccdf53147
CRs-Fixed: 3300183
During Deauth/Disassoc event logging, reason code is being
logged as '0' irrespective of the real reason code.
Modified the api wlan_connectivity_mgmt_event() and
api cm_roam_mgmt_frame_event() to og correct value of
the reason code.
Change-Id: I6d5ba65a9ae312dc82e70202fe598da27a033ff3
CRs-Fixed: 3297871
Currently, supplicant sends roc request and hostapd sends
vdev start request to host driver. After processing these
request, host driver sends it to firmware.
But for ROC request having long dwell time, firmware can not
handle vdev start req as it waits for ROC request completed
(timeout occurs). This is leads to crash in firmware.
So, to fix this issue, host driver aborts p2p roc request
before starting BSS (sending vdev start request).
Change-Id: I956428cf94015ac6c4ff7063ef9b060146e4377b
CRs-Fixed: 3270079
During reassociation, cm_check_for_reassoc_hw_mode_change() is called
to check the coming concurrency is supported or not after preauth is
done. For non-DBS chip, due to STA+STA concurrency is not supported
by FW, the connection manager will run into state disconnecting from
roaming and disconnect current connection by sending disassociate frame,
then do new connection again. It's not normal roaming flow in which
disassociate frame should not be seen over the air.
Per the reassociation flow, it will internally delete previous connection
first, so can call policy_mgr_store_and_del_conn_info_by_vdev_id first to
make sure concurrency checking can pass even if a new STA connection is
coming up.
Change-Id: I5f9f3e1151cb5402405042e3e9f2bec95f0b094c
CRs-Fixed: 3246822
Fill the number of links that need to be forced inactive
when the force mode is MLO_LINK_FORCE_MODE_INACTIVE_NUM.
Change-Id: Ifd24ba213a9cf011535bfd3662dd83e5b584aa51
CRs-Fixed: 3277465
Currently in case STA is up on 5 GHz channel,
2 GHz band is preferred for P2P CLI and SAP when
concurrency priority is throughput and power
instead of SCC channel.
Fix is to prefer SCC channel in case of
throughput an power instead of moving
to another mac.
Change-Id: I0a2eef10e92f277b38e6ae80961e8d6e27047169
CRs-Fixed: 3289767
Two mlo sta link vdev (2+6(LPI)) are started but hw mode is SMM (one
link maybe inactive in fw).
When start SAP on 5 GHz low, driver doesn't select force SCC channel for
such case. It left the SAP channel not changed (5 GHz 5220).
Since the 6 GHz STA link is on LPI mode, SAP is not allowed on
6 GHz (policy_mgr_modify_sap_pcl_for_6G_channels). Driver needs to
consider the PCL as well to select force SCC channel. Add new API
policy_mgr_get_pref_force_scc_freq to fix it.
Change-Id: I824de7168a26955caeeaff955a232c80baa13345
CRs-Fixed: 3280704
Currently, link entry is not added to connection_list of
policy_mgr in case of legacy to MLO roaming. This causes
policy_mgr to miss track of the MLO link.
Check if the connection entry is present in the policy mgr
for the link vdev id and add an entry if it's not present.
Change-Id: Ib19f3616a3384670f1faef20c39476a2bcac2588
CRs-Fixed: 3274435
In STA+SAP concurrency, if the STA is connected in indoor
power, and if the country/channel supports VLP, then bringup
the SAP in VLP. Move the STA to VLP as well.
Restore the power of the STA, when the SAP is disconnected.
Add changes to:
a) Decide the power type for the concurrency during start bss,
stop bss, change channel request calls of the SAP interface.
b) Allow the 6 GHz SCC channel in ACS computation if the channel
supports VLP power or if the channel is indoor and enabled.
Change-Id: I151e2e3e8910a406bb5c1526f4f01715854d173f
CRs-Fixed: 3268100
Currently if SAP is up on 5 GHz DFS/non-DFS channel and country
change happens to world mode where SAP is not allowed on 5 GHz
channels then it moves to a 2.4 GHz channel and saves current
operating frequency band information, now again if a country
change happens SAP tries to move back to the first 5 GHz
active/passive channel.
Sap should come to active channel first. If not available then
it should come on DFS channel, but it shouldn't come up on
passive channel.
To address this issue, add a fix to filter out passive channels.
Change-Id: I32e8a81c2a5d9e785262edbeeef2c879c87f1302
CRs-Fixed: 3277965
Hw mode change in progress is set after the set_hw_mode
command is queued in serialization. Its not reset in below
cases:
Active command timeout case, serialization command
cancelled case.
Before connect request is queued, if hw mode change is in
progress, there is 6 secs wait and if there is no hw mode
change response, connection failure. This causes subsequent
connection failures and there is no recovery.
Reset the wait for hw mode change event in serialization
command failure cases.
Change-Id: I716982f06198e9c3495685ddb158044778c4b1ff
CRs-Fixed: 3256424
Currently rso enable for open and secure connection is handled
incorrectly.
For secure connection roaming should be enabled
after key exchange is complete.
For open connection rso enable is done twice.
Fix is for enabling roam offload for open and secure connection.
Change-Id: I0abde2a6001f176c97e4aa59947260a50c48e6cc
CRs-Fixed: 3271248
In SAP+GO concurrency, if move SAP to DFS channel (BW 160 MHz)
and cause MCC with GO, the target will do CAC on SAP, but target
doesn't support MCC with GO when SAP is CAC state.
Fix by checking correct BW of CSA target channel so that correct
DFS flag can be got and if target channel is DFS causing MCC
with other AP interface then reject CSA request.
Change-Id: Ic7821cf62d3b364e4d2ea052dc82d65d18054091
CRs-Fixed: 3275285
