When dcs triggers acs in STA+SAP mode, dcs detection will be disabled
and acs process will be ignored, but dcs detection won't be restored
again when STA disconnects, it's an issue. Dcs detection and acs
process should work normally when STA disconnects.
Fix is to restore dcs detection when ignore acs in STA+SAP scc mode.
Change-Id: I701fd2eec1d6e293c7c5da460a4e5b13d16c0929
CRs-Fixed: 2784177
Add an INI to configure the wow-mode logging config.
So that,the fw would use this bitmap for logging when it
is in wow mode.
Change-Id: Ib2fbd0c5c9cc573b2f5b12dcdf06682c16550cb2
CRs-Fixed: 2810372
Rename struct wlan_cm_connect_rsp to wlan_cm_connect_resp for
better readability and to avoid duplication of the structure
and function name as there is already a function with the same
name.
Change-Id: I331365058ed25b902aae11f979512b4edcd3ac06
CRs-Fixed: 2809137
Macro ROAM_OFFLOAD_V1 is useless since new rso path code is
used, clean up all ROAM_OFFLOAD_V1 related code.
Change-Id: I0f6f2171a62b5c0cfb5333104be7eabc705dfef8
CRs-Fixed: 2812277
As per vdev state machine, host deletes peer while vdev stop response.
If host deletes peer on wma peer assoc req send fail, vdev state machine
stuck at vdev stop and fails to send vdev down to FW. Thus PE session
and vdev ref of WLAN_LEGACY_MAC_ID remains undeleted. Which leads to
ref leak. Hence do not delete peer if peer assoc req send at wma.
Change-Id: Ibc5d6013fa3ecbad1e45ea03b8d27c9010a72008
CRs-Fixed: 2812183
GENOA FW doesn't support WMI_REQUEST_LINK_STATS_CMDID. So, add this
change to disable link layer statistics for GENOA chip. This change
also fixed compilation issue without WLAN_FEATURE_LINK_LAYER_STATS.
Change-Id: Ib800c9717908767e390ccc234c577a5300f82cf2
CRs-Fixed: 2805832
If IPA driver is not initialized during kernel boot, wlan driver
would be failed to probe because that smmu map setup failed.
Skip this failure to make sure that wlan driver can load
successfully for basic function.
Change-Id: I1e4554908a1603e4b1fce956b153db87859b4ddd
CRs-Fixed: 2786761
When driver working with FTM mode for qca6174, unloading driver
need send WMI_PDEV_SUSPEND_CMDID to firmware, as firmware has no
code to handle this command for FTM mode, driver will do self recovery
after waiting response timedout. Fix the issue to skip pdev suspend
command with FTM mode for specific target.
Change-Id: I9e6ea6de3e8cb15580ba06e1a1a0c0ac7c3a9253
CRs-Fixed: 2785653
Add implementation of hdd_objmgr_get_vdev and hdd_objmgr_put_vdev
api for object ref id tracing enabled.
When WLAN_OBJMGR_REF_ID_TRACE enabled, add line and func name to
the two API to record the ref/deref history.
Change-Id: I7c4c52159d4e1b842026b584ff8f25faa47c168c
CRs-Fixed: 2802668
Move ini CFG_VENDOR_ROAM_SCORE_ALGORITHM from qcacld-3.0 to qcacmn part.
from qcacld-3.0: mac_ctx->mlme_cfg->roam_scoring
to qcacmn: mlme_psoc_obj->psoc_cfg.score_config.
Change-Id: I318f0d516ce699c061f268116e1cbf79fcc9e23a
CRs-Fixed: 2806090
Currently during get_ch_info dot11 mode is fetched from mlme_cfg
and used to calculate phy mode without any band validation which
may cause errorneous behaviour in below cases due to invalid band
and dot11 mode combination:
a.) Band 2g and dot11 mode 11a
b.) Band 5g and dot11 mode 11g
c.) Band 5g and dot11 mode 11g_only
c.) Band 5g and dot11 mode 11b
Fix is to update modes in case mlme_cfg mode and frequency combination
is invalid.
Change-Id: I6390677cb196ebec3695d73cfe1e67086a67a8c0
CRs-Fixed: 2802679
This reverts commit "Change-Id: 5859acc0d6938feaf52516fcc5c18f0bdcab14ab".
Above change is not required on this branch as the issue fixed
with above change is not present on this branch.
And because of the above change there is an issue of priority
inversion between disconnect stats and deauth/disassoc commands.
disconnect stats command should always execute before deauth/disassoc
commands so that peer stats can be retrieved before peer gets
deleted. with current implementation where both the commands have
high priority disconnect stats command will execute first if there
is no active command in the active queue else deauth/disassoc
command will be queued before the disconnect stats command and
if there are multiple clients connected to SAP and all gets
disconnect at the same time, disconnect stats command for all
the clients will be there in the serialization queue, because of
which serialization queue gets full and no other command can be
added to serialization queue.
To address above issue change the priority of the deauth/disassoc
commands so that disconnect stats always gets chance to execute
first.
Change-Id: I7041ddfcb195da5a9e203feb5bbb36e645141630
CRs-Fixed: 2808528
Since new rso ROAM_OFFLOAD_V1 path is enabled, remove
the old rso path code for hdd/sme/lim related files.
Change-Id: I9bb470cb2af0cc940f9c5dd70942eac0cdd83eb5
CRs-Fixed: 2809268
Currently IPSec packets encapsulated in UDP packets
are aggregated via FISA. This is leading to unwanted
behvaior of certain special packets (hearbeat etc)
being aggregated along with other normal packets of
a flow, thereby leading to use-case disruption.
Fix this by not aggregating IPSec packets.
Change-Id: Ieada556e7e3ef67d2c7a8e8ba4d7197c7660be0c
CRs-Fixed: 2783629
Since new rso ROAM_OFFLOAD_V1 path is enabled, remove
the old rso path code for cm/wmi roam related files.
Change-Id: Iec350f032c3e037204f560199d4a6e258ac02688
CRs-Fixed: 2810145
Roaming between different PMF option APs has following issues:
1. Roaming between Optional -> Disabled -> Optional
When STA roam to optional, PMF is set to False from STA in reassoc
request and all management pkt not secured.
2. Roaming between Required -> Disabled -> Required
STA not able to find candidate AP when tried to roam to AP with PMF
Required.
Root cause: When LFR3 roam happens, vdev_crypto_params will be reset
including rsn_caps 11w PMF, if new AP hasn't enabled PMF, vdev rsn_caps
11w PMF is disabled too, and passed to F/W. Then F/W think DUT STA
doesn'tsupport PMF, then failed to roam to AP with PMF Required and
enabled.
Fix:
Get self-capability of 11w PMF from connected profile and pass to F/W in
WMI_ROAM_SCAN_MODE by wmi_fill_rso_tlvs after roaming.
Move target_if_cm_roam_fill_11w_params to csr_cm_roam_fill_11w_params,
put protocol part to csr connection manager.
Change-Id: I543799385ec8c0ec7afdf64e2310c24758305095
CRs-Fixed: 2807454
Add a vendor command to report statistics to userspace
for clear channel assessment.
Change-Id: I5c8ddc14f6661d2af7e4f3a9e1c9c844fd4cd16d
CRs-Fixed: 2773536
Memory is created for the mlme legacy pointer during the create
of the mlme legacy priv object. This allocated memory doesn't get
free when an error condition which leads to device crash.
To avoid this problem memory should be freed before returning from
the error condition.
Change-Id: I8aaaf7bf17cf38f70135e5ff00db429c34aff2d8
CRs-Fixed: 2803896
In 2.4 Ghz, if peer is advertising MCS10/11 in 11ax and doesn't
support LDPC coding then STA downgrades to 11ac but if AP doesn't
advetise MCS 10&11 and LDPC bit is not supported, then STA treats
LDPC as optional in 11ax and would not downgrade to 11ac from 11ax.
Change-Id: I80b4c6615469c21020ed8d671c2d9ec94bd600b4
CRs-Fixed: 2810347
Since new rso ROAM_OFFLOAD_V1 path is enabled, remove
the old rso path code for csr related files.
Change-Id: I6527630951ca1c291e027e7ecdb3f9bf4b0a72b3
CRs-Fixed: 2808325
Steps to reproduce:
1. AP-AP setup on channel 48 in SCC mode.
2. Indicate channel avoid including channel 48.
Observed Results:
Channel avoidance not happened, AP-AP still in channel 48.
Expected Results:
Channel avoidance, AP-AP moved to another safe channel.
Root cause: When channel 48 became unsafe, tried to switch AP1 to safe
channel 36, but failed for AP2 in different channel of same MAC,
wlan_sap_validate_channel_switch return false.
Fix: When CSA for unsafe channel, since get pcl by
policy_mgr_get_pcl_for_vdev_id, scc channel is considered already,
set force to switch channel as true, ignore more SCC/MCC check by
wlan_sap_validate_channel_switch.
Change-Id: I95544d069e5cf3b289e78592f81e0e6496b72801
CRs-Fixed: 2773925
For wow or active offload mode, FW will re-inject some RX frames
to REO with reo_destination_indication 1 (REO2SW1) to REO entrance
ring, but the original reo_destination_indication in RX buffer pkt_tlv
is 6 (REO2FW) or other flow steering value (>=16), then REO2SW ring
mismatch will happen that break FISA function in host.
Bypass FISA if reo_destination_indication mismatch between REO ring
descriptor and pkt TLVS.
Change-Id: I8736b8a96513c2e49fe41fb460f81cb0ef01ed01
CRs-Fixed: 2807461
Add connect and disconnect function call from hdd to osif for
connection manager to enable the connect and disconnect flow for the
connection manager.
Change-Id: I1504410cd431aedf04b58e93d9eeff34040b32a1
CRs-Fixed: 2804230