PASN peer do not get deleted unless the peer is same
as roaming bss peer. Therefore, if peer is not found
during configuration of the ltf key seed, then either
the BSS peer is not yet created or the PASN peer got
deleted because of connection with that BSS.
Either way, PASN auth status need not be sent, therefore
return success if PASN peer is not found during ltf key
seed configuration.
Change-Id: Icb663dd32d3d109a4387dad2ea0c98faf23bebd7
CRs-Fixed: 3475648
For ML-AP, if fastreassoc command is received and scan
candidate is not found in host scan db.
Host will still send roam invoke request to FW, FW will
perform scan.
Change-Id: I8157cf396e3e0c19607d990307e07d31e879a2d4
CRs-Fixed: 3474257
When handling T2LM action request frame, clear the previous
ml peer level t2lm negotiation before applying new tid mapping
to FW.
Change-Id: Ie7f7a28fb7cf886778cd697605352c4ff47d18fd
CRs-Fixed: 3487089
Since the qcacld-3.0 driver is not part of the upstream kernel, the
Kconfig has not been used for driver configuration. As a result, it is
missing hundreds of configuration options that are now supported by
the driver.
The upcoming Bazel DDK build infrastructure *will* use the Kconfig
file. In preparation for populating the Kconfig, sort the existing
options in alphabetic order to facilitate the addition of the missing
options in a subsequent patch.
Change-Id: I7a714d373ae601b8c6642c224aca6b64da618ecd
CRs-Fixed: 3487378
Change I66d159a1594f71fdf33f3e4b4e6be4840d7e140a ("qcacld-3.0: Include
change Ids in build tag") replaced the usage of CONFIG_BUILD_TIMESTAMP
with CONFIG_BUILD_TAG. However, that change did not actually modify
the Kconfig item, so do it now.
Change-Id: Id69a339a8d539b3cd5b455c411ae10652f6aa897
CRs-Fixed: 3487377
Changes I0045dcccd36524cbcd4253347c9e0a5704193c2b ("qcacmn: Combine
all NAN related flags with WLAN_FEATURE_NAN") and
If98ecaace17f8724e9c28325ef61e721f42e1d8f ("qcacld-3.0: Combine all
NAN related flags with WLAN_FEATURE_NAN") removed all usage of
WLAN_FEATURE_NAN_CONVERGENCE, but did not remove it from Kconfig or
from all defconfigs, so do that now.
Change-Id: Ib19f30d2be5c2ddaad13a2526442d3d7266e4754
CRs-Fixed: 3487376
Change Id3a2127e9ecb343ad2a0354dcbc331c22167d7fb ("qcacld-3.0: Remove
feature flag WLAN_FEATURE_11W for pmf") removed all of the conditional
code for CONFIG_WLAN_FEATURE_11W. However, the actual Kconfig entry
was not removed, nor was the configuration setting removed from the
defconfig files, so do that now.
Change-Id: I0ba83841346fc47673231fba6aa22da9317caf09
CRs-Fixed: 3487375
The PRIMA_WLAN_OKC feature is not applicable to qcacld-3.0, so remove
the feature flag.
Change-Id: Ia0dcfd34c18c31ecb6a270ede6f398160772cef7
CRs-Fixed: 3487374
The compiler switches defined by DFS_INC are being included in the
composite INCS twice. This results in the switches being unnecessarily
duplicated in the compiler command line. While this normally doesn't
affect compilation, it can result in a "command too long" error that
has been observed in some build environments, so remove the
duplication.
Change-Id: Ibe09e7c3d4ba1a9b5b50305c73b79ce1c9a7d57a
CRs-Fixed: 3487038
After ML STA connected on 2.4 GHz + 5 GHz, two existing
SAP (2.4 GHz and 5 GHz) have to force SCC to respective
band's ML link home channel. Currently driver make the
CSA for two sap at same time but to different channel.
We only support CSA one by one (for different target
channel) because only one target channel is in
mac_ctx->sap.SapDfsInfo.target_chan_freq. Otherwise, the
value will be override by second SAP's CSA and causes
first SAP changed to wrong channel.
Fix by:
1. change __policy_mgr_check_sta_ap_concurrent_ch_intf to
trigger CSA for one SAP by break the loop.
2. reschedule the sta_ap workqueue after first CSA done in
multiple SAP case. Then do force SCC for second SAP.
Change-Id: I1de81b5839a7e24f862627ecc49663dcd0d91ce4
CRs-Fixed: 3470343
As per requirement, for MLO connection host should reject
GET_CU_FOR_EACH_SUB_BW request and return failure to upper
layer as a response.
Change-Id: I8177d92982c832a17c1657239b69cc3712e1eaf4
CRs-Fixed: 3476349
While reviewing build artifacts it was observed that the compiler
command line has a badly formed -I switch:
-I[path]/qcacld-3.0/cmn/-I[path]/cmn/target_if/gpio
Analysis of Kbuild shows that an already formed -I switch is being
incorrectly used as a directory, so remove that specific entry.
Change-Id: If59e8ee1d0f817bc8c56e74bc8e2fa9ef94a7eb3
CRs-Fixed: 3486972
Diag logging is used for connectivity logging of
BTM event.
Remove unused legacy connectivity logging mechanism for
BTM events.
Change-Id: I65dc5fe5f071fd74eeed2433894a238318ce76ab
CRs-Fixed: 3470401
Diag logging is used for connectivity logging of roam
candidate event and roam roam result event.
Remove unused legacy connectivity logging mechanism for
roam candidate and roam result events.
Change-Id: I826107fc764abdeec7408dbb6c52e580d1fe32f4
CRs-Fixed: 3470206
As per draft 3.0, association or reassociation request
or response can include upto 2 t2lm ie's.
Change-Id: I2095e161c433237ce91ab25d1bd133e0bb5f106f
CRs-Fixed: 3487012
Scenario: There is dual sta present in HBS mode in DUT where one
sta is on wlan0 interface and it has 11be capability, so it has
formed ML connection with ML AP. The another STA is present on
wlan1 interface and this STA also supports 11be capability. But
as per current design, host supports 11be with MLO. It doesn't
support 11be alone. Also 11be with MLO is supported only in wlan0
interface. So for another connection which are present in wlan1
interface, even if it supports 11be host will downgrade to 11ax
and form connection.
During the formation of second connection, host will sends peer
create command(WMI_PEER_CREATE_CMDID) to firmware. Before sending
this command, host checks only eht cap in cm_create_bss_peer()
and fills the mld_mac addr. Because of that, DP assumes that
there is an ML connection and it creates MLD peer on wlan1
interface. Due to this, it causes ping failure on wlan1 interface
as the ICMP response might be coming on incorrect peer and it's
getting dropped.
As part of fix, check whether vdev is mlo supported or
not in cm_set_peer_mld_info()
Change-Id: Ieed67aa2735d200a140f9e771d791b3b9308a0f9
CRs-Fixed: 3474874
In the case of an ML SAP SAE connection, if the reference
STA is a non-ML, the driver should not perform SAE address
conversion. Currently, during SAE Auth commit RX, if the
ML IE is not present in the frame, the driver decodes an
incorrect peer MLD address and saves it in the pre-auth
node structure. Later, userspace sends the SAE Auth commit
TX frame, and the driver fails during pre-auth node search
due to the incorrect MLD address saved in the pre-auth node,
which leads to SAP connection failure.
As part of the fix, the driver should decode the correct
peer MLD address or set it to 0 if the ML IE is not present.
Change-Id: I335361dca50969c7ee25a502732ae3f29cc99eff
CRs-Fixed: 3481176
Add API to get LI which is configured by the user.
In case, user has not configured any interval,
device uses default LI and this cmd will return 0
Syntax for cli cmd: driver GET_LISTEN_INTERVAL
Change-Id: I3ef12ffc757288c057c88dceece7dbc2da68880b
CRs-Fixed: 3425472
If STA connected with MLO AP, don't process ch_width update
with notify request.
Change-Id: Id2e0d6357feac13787abcafe8b9d69a0c64dbedb
CRs-Fixed: 3472173
Host receives QCA_WLAN_VENDOR_ATTR_CONFIG_CHANNEL_WIDTH vendor
command indication to update STA adapter channel width.
On receiving channel width update indication from upper layer,
first host updates internally and send new channel width value
to FW via WMI_VDEV_PARAM_CHWIDTH_WITH_NOTIFY.
Target firmware should take care of notifying associated peers
(except TDLS) about change in bandwidth, through OMN/OMI
notification before performing bandwidth update internally.
Change-Id: I517ed1fbf8d074e511f8fb43c9c1dac824c9f084
CRs-Fixed: 3469473
In case of wide band scan request, FW sends subband CCA busy info
to host via a new tlv wmi_cca_busy_subband_info added in existing
event WMI_CHAN_INFO_EVENTID.
Fix is to store CCA busy info coming from FW to HDD context.
Change-Id: Ic4b439ed1c270badbe265dc8543dc6d6a1612fab
CRs-Fixed: 3469467
Currently the CONFIG_WLAN_DIAG_VERSION is not being set in the
peach defconfig, causing compilation errors for peach builds.
Fix this by replacing duplicate CONFIG_WLAN_DEBUG_VERSION
with CONFIG_WLAN_DIAG_VERSION.
Change-Id: I1fc2fcfc987d63c3f038e41652ea4c43667bbe42
CRs-Fixed: 3483501
Diag logging is used to log mgmt frame events.
Remove unused unused legacy connectivity log used
for mgmt frame events.
Change-Id: I7d682f9aa4005d82beef03030017f943687e3480
CRs-Fixed: 3469403
Diag logging is used for logging connectivity
events,
Remove legacy logging mechanism for connectivity
events
Change-Id: I85bbb1cb88e8a3c1d4357e9b732642ca8f5fe95a
CRs-Fixed: 3469396
When create virtual interface, if psoc idle restart return failed,
close adapter without calling wlan_hdd_release_intf_addr,
addr is leaked and used out.
When SAP start, create virtual interface wlan2 will fail for
MAC is not available.
To fix it, when create virtual interface failed, call
wlan_hdd_release_intf_addr before close adapter.
Change-Id: I84493985eaa7dda5b8b620c7e86bdf94c89ce2f8
CRs-Fixed: 3480866
As the IPA component has moved out of kernel,
WLAN currently does not have access to the IPA
header files that was previously part of kernel.
To resolve this, WLAN needs to include the path
to IPA header files, for successful compilation when
IPA_OFFLOAD is enabled. With this Kbuild change
now WLAN can support OUT-OF-TREE IPA module.
Change-Id: I56f66d3e7d7648ece5aeb68de1af7c0c5f59f84d
CRs-Fixed: 3482432
The WLAN_OPEN_SOURCE flag is a legacy flag which had a specific use
that is no longer applicable. So remove all usage of that flag.
Change-Id: If51b9421717bc82b3c200c6412a87b0e46a77476
CRs-Fixed: 3464926
Add support to stop t2lm timer during sta disconnection
and clear t2lm mapping.
Change-Id: I59e724331eda8b67fd1405031bdb00d12805ad09
CRs-Fixed: 3479496
