Change 1. In the API hdd_get_roam_chan_from_fw
Changed the return type form static uint32_t to static int
Change 2. In the API set_first_connection_operating_channel
Changed the wrong return value -EINVAL to return set_value
Change 3. In the API set_second_connection_operating_channel
Changed operating_channel == 0 to !operating_channel and
return -EINVAL to return set_value
Change 4. In the API hdd_update_tgt_cfg
Removed the unused variable status = false
Change 5. In API sme_set_ht2040_mode
Changed the cb_mode condition from if(!session->cb_mode) to
session->cb_mode==PHY_SINGLE_CHANNEL_CENTERED
CRs-Fixed: 3891029
Change-Id: I697a915bf10ed2b331198a1621f75ffe7259628d
-Add check for new hw modes, while advertising emlsr capability
in mlo ie and assoc request.
-Add new config emlsr feature flag for ganges.
CRs-Fixed: 3636676
Change-Id: I13038efe4d5001d480ae24fe7da135474eb8a3f1
Fix possible race condition in data->type value in case of multithreaded
listener or app IOCTLs.
For example, below could cause inconsistent data->type value while
racing belows IOCTLs
Thread1 with QSEECOM_IOCTL_REGISTER_LISTENER_REQ
Thread2 with QSEECOM_IOCTL_UNREGISTER_LISTENER_REQ.
Change-Id: Id4f0ffcbff70bfbf13423f9f080fbaf51759ad82
Signed-off-by: Nishant Pandey <quic_nishpand@quicinc.com>
Signed-off-by: Divisha Bisht <quic_divibish@quicinc.com>
Driver re-generates the RSNXE with length 1, if the peer AP
supports only 1 octet of RSNXE. During this IE creation,
driver creates an empty RSNXE if none of the caps are set
by userspace in the first octet.
To fix this, do not re-generate the RSNXE if none of the caps
are set in first octet.
Change-Id: I6ca855cd907e49af62d9afe804b9f73eea97332e
CRs-Fixed: 3901178
In lim_send_probe_req_mgmt_frame(), validate the pe session
before accessing it.
Change-Id: I96ebfc62c04e2e7323017732b6208da83919346c
CRs-Fixed: 3880869
Currently, the get_current_groups API accesses group info, which
increases the usage refcount. If the IOCTL using the
get_current_groups API is called many times, the usage counter
overflows. To avoid this, access group info without taking a
reference. A reference is not required as group info is not
released during the IOCTL call.
Change-Id: Iec31c90f9fd1a837fb697d5d7d1baba7d285374d
Signed-off-by: ANANDU KRISHNAN E <quic_anane@quicinc.com>
remove the gsi pending irq check for xr platform as we are observing
discrete ieob irq set for wdi use case and in a way it is taken care
by msi interrupts.
Change-Id: I306cad1f63cd9cf156567fc6b0cb210f7bf0152c
Signed-off-by: Jagadeesh Ponduru <quic_jponduru@quicinc.com>
Retrieve the HFI queue payload size parameter directly
from synX driver and update it to uC.
Change-Id: I6ab34853f92740795fd0de6c2a144707facca7e7
Signed-off-by: Prasad Arepalli <quic_parepall@quicinc.com>
allow both tcp and udp protocols when we install wlan filters
through ipa debugfs nodes.
Change-Id: I543b7b914fe3f15f53ba3e6baca9bc93147f398c
Signed-off-by: Jagadeesh Ponduru <quic_jponduru@quicinc.com>
Currently, qdf_set_bit()/qdf_clear_bit()/qdf_test_bit() APIs are
used to operate on the event_flag in logger_thread. These APIs
use non-atomic kernel APIs __set_bit()/__clear_bit()/__test_bit()
and the operation is indeterministic when system syspend/resume
happens.
Use atomic APIs(qdf_atomic_*) to avoid this.
Change-Id: I52d1c608f9845ed6c98975f2455035c8587bfd72
CRs-Fixed: 3890216
(cherry picked from commit 3aaddb2c45)
Currently, wakelock is taken for all unicast packets.
Do not take wakelock if packet is IP multicast packet.
Change-Id: If197cbb58d1414adedb1d29f9c2bd67be83e95b4
CRs-Fixed: 3807621
Currently, wakelock is being taken for all unicast packets.
Do not take wake lock if it is a ARP packet but not local to
host.
Change-Id: Iff5de2b83a4b12692b2f3b82d58e0fc400326529
CRs-Fixed: 3838502
IP multicast check for IPv4 was failing as the big endian
conversion was not being done and wrong values were being checked.
Do ntohs conversion on macros to check if packet is mcast packet.
In IPv6 check, the word is being checked instead of first byte.
Check only first byte when checking for ipv6 multicast address.
Change-Id: I686cdef7957778f9c60f2dc919421d39c4b8b71c
CRs-Fixed: 3824229
This reverts commit 9184f0dbd383af314112f1f6038a4143c44a5837.
Reason for revert: Janks are observed with bouncing ball test.
Change-Id: I5fd3dd5c7abf83cdaa141ccc42271e3ff899cfce
Signed-off-by: Anand Tarakh <quic_atarakh@quicinc.com>
When MLO STA connects to a specified buggy MLO AP with PMKID in assoc
req, it consistently fails and then retries with a downgraded SLO
candidate, which eventually succeeds. However, the customer expects MLMR
connection.
To address this, when select this buggy AP, we avoid generating
downgraded SLO/11AX candidates, use full SAE auth instead of existed
PMKSA, and don't add PMKID in RSNIE of assoc req when connect.
If the MLMR assoc fails, assoc rejection is sent to upper layer,
not retry with SLO/11AX candidates. Instead, wpa_supplicant/aosp will
clear the PMKSA upon receiving an association rejection, and subsequent
retries will use full SAE authentication, resulting in a successful MLMR
connection.
Change-Id: I85f39f52e4dae8393bbf559969710f35447b8c0c
CRs-Fixed: 3888073
When MLO STA connects to a specified buggy MLO AP with PMKID in assoc
req, it consistently fails and then retries with a downgraded SLO
candidate, which eventually succeeds. However, the customer expects MLMR
connection.
To address this, when select this buggy AP, we avoid generating
downgraded SLO/11AX candidates, use full SAE auth instead of existed PMKSA,
and don't add PMKID in RSNIEof assoc req when connect.
Change-Id: I8e446544b2fdbae089840713bc8bc93c601f1863
CRs-Fixed: 3888074
When util_scan_copy_cache_entry return NULL for out of buffers,
NULL pointer dereference happens.
To fix it, check return pointer of util_scan_copy_cache_entry
before use it.
Change-Id: Iec5e6f10c8e0bbe6b88d844cc00320f3f23191a4
CRs-Fixed: 3885075
Currently, When connection failure happens with MLO
AP then all combinations of that MLO AP are tried until
the partner links become 0/SLO.If AP configured links are
more than supported links and AP doesn't support EHT then
AP disconnects with reason EHT not supported and STA will not
be able to connect to that AP as STA tries combination till SLO
but all combinations are 11BE only.
To Fix above scenario add a 11AX entry in candidate table, so that
connection can be tried with 11AX if all combination fails or failure
reason clears that 11BE association is not possible.
Change-Id: Ibde68f44a1367c9af160201bc677dd97b1897c06
CRs-Fixed: 3779644
There could be a case when SLO and 11AX entry has same score. In
that case consider MLO candidate first and then move to 11AX in case
of failure.
Change-Id: I4e24ff45a23e9f620b7c2894f26223c55828c8bd
CRs-Fixed: 3779623
As current MLO RSSI algorithm, MLO RSSI score is quite worse
than that of better link if worse link RSSI is poor, which may
make MLO candidate score worse than link candidate score, SLO
candidate is selected to connect instead of MLO candidate.
To fix it, for DBS/HBS MLO candidate, boost total score 10%.
Optimize MLO rssi score algorithm as following:
MLO-RSSI = [BW1/(BW1+BW2) ]* RSSI1 + [BW2/(BW1+BW2) ]* RSSI2.
CRs-Fixed: 3776301
Change-Id: I16d65b2a70cd0ca0daba47b116c8627f995d5157
Currently CONFIG_PLD_SNOC_ICNSS_FLAG and CONFIG_ICNSS2_HELIUM
configs are not enabled in Bazel GKI config file of Adrastea for
parrot66 target. As a result host is not calling relevant PLD
API for driver registration during load. As a result seeing
Adrastea driver loaded for Moselle device.
To address this issue, enable CONFIG_PLD_SNOC_ICNSS_FLAG and
CONFIG_ICNSS2_HELIUM configs.
Change-Id: I7419eb1f6339e134a85729f25301913adf02e484
CRs-Fixed: 3898745
