User reads policy manager connection status information via sysfs
entry. Host adds HW mode dbs capability information in pm_cinfo
by checking HW is dbs capable and present HW state is DBS.
Change-Id: I00d83b49dfae41b17341d3758d8ead42ffd602a8
CRs-Fixed: 2795010
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
In FISA path number of list elements in head nbuf is not updated,
leading to wrong calculation of dp thread stats and packets are dropped.
Update the number of list elements in head nbuf before flush.
During calculation of outstanding packets to be processed
by dp rx thread take rx flushed packets into consideration.
Change-Id: Id96ceee71e035fdbe17f0da4b662c6f848296fbd
CRs-Fixed: 2811001
Currently net_device is being validated inside the
hdd_for_each_adapter_dev_held_safe loop. This is not required as
hdd_for_each_adapter_dev_held_safe will hold the reference for
net_device and prevent it from being deleted. So net_device validation
is not required inside hdd_for_each_adapter_dev_held_safe loop.
Change-Id: Id7e78748b80e7a3bbe50fee43a28fd0d48bd6856
CRs-Fixed: 2812716
The event WMI_ROAM_STATS_EVENTID is received after
every roam, once the roam synch complete is sent by the host.
This event contains details regarding the btm response.
This helps to debug the scenario when roam failure happen.
Print the info received related to roam scan type & roam status
info into kmsg.
Change-Id: Idd688eb4d1e699573fa1e243873c30ffdc5bf96f
CRs-Fixed: 2794555
New files are created for 6ghz scan functionality. Add the same
for compilation.
Change-Id: I3f715db50fb5020afea74297794d07ddc5b39913
CRs-Fixed: 2806415
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
Wake lock stats vendor command attribute names
in the driver are different from the attribute
names in upstream qca-vendor.h.
Change the wake lock stats attributes name in driver.
Change-Id: If9dbd46482f2f65758ea90aebdd078c1a30d5bef
CRs-Fixed: 2789539
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
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
This reverts commit "Change-Id: 5859acc0d6".
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
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 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
Enable pld_smmu_unmap support for ICNSS2 Adrestea targets.
This is needed to enable SMMU-S1 geometry support.
Change-Id: I8aa612810cc468269fa5c633276f9b3ba8135542
CRs-Fixed: 2808041
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 lithium GRO is not supported with rx_thread
disable. Add similar handling as part of runtime
rx_thread disable.
Change-Id: I897179ecdfd83f8dde7cd997e943ffb276b1afad
CRs-Fixed: 2794023
Pdev is created once all the modules are enabled and currently
it is freed after the cds close is done, if some of the modules
as part of the de-init sequence has to send a command to the firmware
it will result in error.
To keep the deinit sequence opposite to that of init close/destroy
the pdev before closing the cds.
Change-Id: I8e087a573112e5d2d81e8ea413044d45f228813e
CRs-Fixed: 2797344
Use separate hang reason for case that lack of credit after suspend.
Meanwhile add hang buf offset check to avoid overflow.
Change-Id: Ic794d02672cd663598da66b9e75924c41b5ef0e8
CRs-Fixed: 2801343
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
Currently we configure the REO ID in the HW FST entry,
which is later used by HW to route the packets matching
this particular flow.
Such a kind of configuration can lead to incorrect
routing of packets incase the RX path mapping is
changed (eg when IPA is enabled).
Hence to fix this issue, use the reo destination
indication which is received in the first packet of
the new flow in the HW FST entry.
Change-Id: Ide230dcfb07862b3921aeb02d83ad7c30cb284c2
CRs-Fixed: 2803828
User requests for last disconnect reason code using
QCA_NL80211_VENDOR_SUBCMD_GET_STA_INFO vendor command. Host replies with
connect fail reason codes from enum qca_sta_connect_fail_reason_codes using
QCA_WLAN_VENDOR_ATTR_GET_STA_INFO_CONNECT_FAIL_REASON_CODE attribute, If
last connection attempt failed.
Change-Id: I723a9dcf025bb58fa524cbf16f16a7dcea8bd5b6
CRs-Fixed: 2799227
FTM mode does not create vdev. So in order to add support for the
unit test command in FTM mode, set vdev of the adapter to 0 and create
a new funciton that handles the command called in FTM mode and does
not check for a valid vdev.
Change-Id: I5b71765dc4c6eb8025aa60726e4105f8ff30f634
CRs-Fixed: 2805415
SAP cannot be turned back on, if SAP is turned off during the
Pre-CAC. Because in __wlan_hdd_del_virtual_intf(), cleanup of SAP
is not done.
To avoid this issue cleanup SAP interface also in this scenario.
Change-Id: I12240c22a2b40c2a1fc8a46ff197023abf36631a
CRs-Fixed: 2803454
CAC timer is only created for non-offloaded CAC case, but in some
cleanup functions, CAC timer is stopped/destroyed without checking CAC
offload flag.
Change-Id: If8422afac2389e134769a762aa87cb7969eef9ec
CRs-Fixed: 2807650
