qcacld-3.0: Allow firmware to auto detect tx bssid

In the case of of 5 GHz + non-tx 6 GHz MLO connection, the scan entry
generated from the ML-probe might not carry MBSSID information of the
non-tx

qcacld-3.0: Allow firmware to auto detect tx bssid

In the case of of 5 GHz + non-tx 6 GHz MLO connection, the scan entry
generated from the ML-probe might not carry MBSSID information of the
non-tx partner. The RNR of the assoc link will also not be inherited.
Therefore, the mbssid info is not generated for this non-tx 6 GHz scan
entry. In such cases, if there is a vdev restart, host driver sends zero
mac address in trans bssid, leading to issues with connection.

To fix this:
1. Look up the RNR db for the 6 GHz link, and determine if the bss param
corresponding to the bssid is non-tx MBSSID.
2. If it is a non-tx MBSSID and there is no mbssid info in the scan cache,
then configure the tx-bssid as broadcast mac.
3. This allows the firmware to auto-detect the tx bssid from the upcoming
beacons.
4. Also, save the neighbor entries from the beacon/probes received from
the firmware during roam sync and other events to facilitate the look-up.
5. If there is no existing entry for the roamed non-tx link, then caching
the neighbor info from the assoc partner link would store the valid entry
into the rnr db.

Change-Id: Ie5ef03fc8504cd63f6db98d2ce4af7eb5c2d7e00
CRs-Fixed: 3789675

show more ...

qcacld-3.0: Optimize CONNECTING connectivity log

In the api wlan_connectivity_sta_info_event(), the
CONNECTING connectivity log is printed after
STA_INFO connectivity logs. But this behaviour is
no

qcacld-3.0: Optimize CONNECTING connectivity log

In the api wlan_connectivity_sta_info_event(), the
CONNECTING connectivity log is printed after
STA_INFO connectivity logs. But this behaviour is
not expected during STA INFO Log after roaming
as CONNECTING log should be printed only when
connect request is received from the userspace.

Modify the api wlan_connectivity_sta_info_event()
and logging CONNECTING event from the api
lim_process_mlm_join_cnf() in order to prevent
connecting log during roaming.

Change-Id: I91d2c14b109fb8a828ba99a021fe6b6e462516c8
CRs-Fixed: 3680502

show more ...

qcacld-3.0: Optimize GC connection speed by skipping JOIN

Currently STA/GC connection will have JOIN which actively probe AP/GO
in this state to get latest bss entry, but before connection scan
alre

qcacld-3.0: Optimize GC connection speed by skipping JOIN

Currently STA/GC connection will have JOIN which actively probe AP/GO
in this state to get latest bss entry, but before connection scan
already trigger and bss entry updated in scan db so can skip JOIN
in some scenario.

There is requirement to optimize GC connection speed, and to skip
JOIN state is one of the subtask to achieve it. Add a build option
to skip JOIN for GC connection.

Change-Id: I1f8beaa41ea398601a17fa80997029b8ac8849ae
CRs-Fixed: 3598283

show more ...

qcacld-3.0: Initialize wlan_channel struct before use

In lim_update_mlo_mgr_ap_link_info_mbssid_connect(),
'channel' variable of type 'struct wlan_channel' is
used without initialization.

Fix is to

qcacld-3.0: Initialize wlan_channel struct before use

In lim_update_mlo_mgr_ap_link_info_mbssid_connect(),
'channel' variable of type 'struct wlan_channel' is
used without initialization.

Fix is to initialize 'channel' structure = {0} on
declaration.

Change-Id: I3a6240396cf40ffa0c98f8a825cebd3dfe9f43c3
CRs-Fixed: 3663304

show more ...

qcacld-3.0: Use correct AP BSSID in MLO mgr info for MBSSID

Join request in pe_session stores AP BSSID in link_addr field
but following API is using ap_link_addr field to fill AP BSSID
in MLO manage

qcacld-3.0: Use correct AP BSSID in MLO mgr info for MBSSID

Join request in pe_session stores AP BSSID in link_addr field
but following API is using ap_link_addr field to fill AP BSSID
in MLO manager during MBSSID AP params update which contains
NULL BSSID.
API: lim_update_mlo_mgr_ap_link_info_mbssid_connect()

Pairwise keys are added only if the AP BSSID is valid and since
the AP BSSID is NULL in this case the pairwise is not added for
partner VDEV and once partner VDEV connect is completed pairwise
is not sent to FW which leads to data stall if transmitting on
partner link.

Use the link_addr field which has AP BSSID to update MBSSID info
in MLO manager.

Change-Id: Ib65d1c9d493a0a871fb81bb5ec7f058c24f5f9fd
CRs-Fixed: 3654907

show more ...

qcacld-3.0: Fix for Interop issue in hidden BSS

In hidden SSID case, some IOT AP does not respond to the
unicast join probe requests and this leads to continuous
connection failures. The same AP how

qcacld-3.0: Fix for Interop issue in hidden BSS

In hidden SSID case, some IOT AP does not respond to the
unicast join probe requests and this leads to continuous
connection failures. The same AP however responds to broadcast
probe requests. The host announces join success only if the
probe response is received for the hidden SSID connection.

To fix this, after sending 3 unicast join probe requests, send
the pending probe requests as broadcast to proceed with to get
a probe response.

Change-Id: I686cbabd3b1b3d355829bc682de5d631b1738d86
CRs-Fixed: 3647028

show more ...

qcacld-3.0: Send STA_INFO connectivity event after roaming

Driver sends STA_INFO event with self mac addresses for each link
before initial connection. With the new requirement to send the
STA_INFO

qcacld-3.0: Send STA_INFO connectivity event after roaming

Driver sends STA_INFO event with self mac addresses for each link
before initial connection. With the new requirement to send the
STA_INFO after every roam to detect the change in mac address, add
the sta info call after reassoc response is received and roaming
status is successful.

CRs-Fixed: 3653662
Change-Id: I18ecbdfea47fb3524154f799ea0c4777276cb34a

show more ...

qcacld-3.0: Populate MLO mgr link info for MBSSID connect

In api wlan_connectivity_sta_info_event(),and in
connectivity_mgmt_event() the band information, link self mac
address is populated from the

qcacld-3.0: Populate MLO mgr link info for MBSSID connect

In api wlan_connectivity_sta_info_event(),and in
connectivity_mgmt_event() the band information, link self mac
address is populated from the MLO mgr link info structure. But
MLO mgr link info is updated when we receive unicast probe
request from the AP. But we don't send unicast probe request to
MBSSID non-TX BSS and we could receive beacon from TX BSSID. This
causes the advertised links band information not getting logged
for the assoc request frame connectivity log and STA information
event doesn't have the self link addresses.

Populate MLO mgr link info before sending Join confirm during
MBSSID connect for non-TX BSSID. Introduce a new api
lim_populate_partner_link_chan_info_for_mbssid(), to populate
the link info from join request.

Change-Id: I6148a8a9b9bf15de65e7640f39456dade2e8987f
CRs-Fixed: 3647725

show more ...

qcacld-3.0: Send set tpc power command to fw after roam

Currently host doesn't send set tpc power command to
fw for roam case, hence STA tx power remains same
even if new connection frequency has di

qcacld-3.0: Send set tpc power command to fw after roam

Currently host doesn't send set tpc power command to
fw for roam case, hence STA tx power remains same
even if new connection frequency has different tx
power values.

To address this issue send set tpc power command to
fw while processing roam sync indication.

Change-Id: Ief565760085b0628e6ad2fe40086e7514b9baec5
CRs-Fixed: 3635222

show more ...

qcacld-3.0: Disable puncture in US LPI mode

Disable puncture in US LPI mode per FCC request.
If bad FCC AP is detected, send WMI_VDEV_PARAM_CHWIDTH_WITH_NOTIFY with
reduced bw after setkey is done.

qcacld-3.0: Disable puncture in US LPI mode

Disable puncture in US LPI mode per FCC request.
If bad FCC AP is detected, send WMI_VDEV_PARAM_CHWIDTH_WITH_NOTIFY with
reduced bw after setkey is done.

Also add the same bad FCC AP detection logic in HDD where bw increase req
from SS framework is handled.

When handle beacon update, also FCC AP detection logic to avoid wrong
channel switch.
If the AP removes or reduces puncturing pattern in new beacon, send
WMI_VDEV_PARAM_CHWIDTH_WITH_NOTIFY with increased bw.

For roaming case, after roaming, host will receive new beacon with new
bpcc, same as beacon update, use the same bad FCC AP detection logic and
send WMI_VDEV_PARAM_CHWIDTH_WITH_NOTIFY with updted bw right away or after
setkey is done (in case of hybrid roaming like OWE).

Change-Id: I6e85de879575d5c0a1960527f9018b4b33bf18d6
CRs-Fixed: 3631634

show more ...

qcacld-3.0: Use partner info from pe_session for link switch

After roaming from legacy/1 link ML AP to 3 Link AP, then the
ML pe_session->lim_join_req->partner_info is not updated for
the link vdev.

qcacld-3.0: Use partner info from pe_session for link switch

After roaming from legacy/1 link ML AP to 3 Link AP, then the
ML pe_session->lim_join_req->partner_info is not updated for
the link vdev.
This causes disconnection after roaming from legacy/1 Link AP to
3 Link AP followed by link switch due to link switch connect
failure.

lim_join_request is used to check partner info in some API.
Use session->partner_info instead of lim_join_request as the
lim_join_request is not valid & could be NULL also after roaming.

Change-Id: I1cb0e386cf715c43bcb8b8e05785c5c7d18f53dd
CRs-Fixed: 3627683

show more ...

qcacld-3.0: Modify STA info event to log after join confirm

In api lim_process_probe_rsp_frame(), the STA INFO event
is logged after receiving the probe request. However, the
STA info event is not l

qcacld-3.0: Modify STA info event to log after join confirm

In api lim_process_probe_rsp_frame(), the STA INFO event
is logged after receiving the probe request. However, the
STA info event is not logged for MBSSID case as unicast
probe request is not sent by the STA.

Modify api lim_process_mlm_join_cnf() to send STA info
event to be logged after successful join confirmation
from MLM irrespective whether unicast probe request is
sent or not.

Change-Id: I2c48c0d1ad89dc1a3cbda51a6e1a5f3cd59196ee
CRs-Fixed: 3635957

show more ...

qcacld-3.0: Set vdev start failure before deliver VDEV EV_START_REQ_FAIL

The lim_handle_sme_join_result will set mlme connection failure to true
before delivering event WLAN_VDEV_SM_EV_START_REQ_FAI

qcacld-3.0: Set vdev start failure before deliver VDEV EV_START_REQ_FAIL

The lim_handle_sme_join_result will set mlme connection failure to true
before delivering event WLAN_VDEV_SM_EV_START_REQ_FAIL when substate is
SS_START_START_PROGRESS, it might call wma_send_vdev_stop, which will
reset mlme connection failure to false again.

Set vdev start failure to true in the lim_handle_sme_join_result to
let wma_mlme_vdev_notify_down_complete do not free the data due to this
data is not allocated in the heap in the lim_handle_sme_join_result.

Here is the potential call stack for your ref as below which might free
the local variable param allocated in the lim_handle_sme_join_result:

[ 6776.197093] Call trace:
[ 6776.197152] __ksize+0x24/0xd0
[ 6776.197518] __qdf_mem_free+0x28/0x88 [wlan]
[ 6776.197880] wma_mlme_vdev_notify_down_complete+0xe4/0x180 [wlan]
[ 6776.198413] vdevmgr_notify_down_complete+0x54/0x68 [wlan]
[ 6776.199008] mlme_vdev_state_init_event+0x88/0x1c8 [wlan]
[ 6776.199353] wlan_sm_dispatch+0x168/0x1e8 [wlan]
[ 6776.199697] mlme_vdev_subst_start_start_progress_event+0xf8/0x1d0
[ 6776.200087] wlan_sm_dispatch+0x168/0x1e8 [wlan]
[ 6776.200458] wlan_vdev_mlme_sm_deliver_evt+0x60/0xf0 [wlan]
[ 6776.201043] lim_handle_sme_join_result+0xd4/0x104 [wlan]
[ 6776.201523] lim_process_mlm_join_cnf+0x84/0xc8 [wlan]
[ 6776.201855] lim_process_switch_channel_rsp+0x4a4/0x7cc [wlan]
[ 6776.202186] wma_handle_channel_switch_resp+0x114/0x2d0 [wlan]
[ 6776.202969] wma_vdev_start_resp_handler+0x38c/0x6e0 [wlan]
[ 6776.203866] vdevmgr_vdev_start_rsp_handle+0x48/0x58 [wlan]
[ 6776.204520] tgt_vdev_mgr_start_response_handler+0x68/0x128 [wlan]
[ 6776.206127] target_if_vdev_mgr_rsp_timer_cb+0x27c/0x4c4 [wlan]
[ 6776.208182] target_if_flush_psoc_vdev_timers+0x74/0x270 [wlan]
[ 6776.209455] wma_cleanup_vdev_resp_and_hold_req+0x24/0x64 [wlan]
[ 6776.209752] scheduler_target_if_mq_handler+0x4c/0xbc [wlan]
[ 6776.210048] scheduler_thread_process_queues+0x11c/0x3cc [wlan]
[ 6776.210344] scheduler_thread+0x9c/0x1e8 [wlan]
[ 6776.210677] kthread+0x16c/0x17c
[ 6776.210784] ret_from_fork+0x10/0x18
[ 6776.210879] Code: f2bffc09 d346fd08 f2dfffc9 927acd08 (f8696909).

Change-Id: I058d4f5e8526209d9bb17102a96be6625e1307e6
CRs-Fixed: 3614659

show more ...

qcacld-3.0: Use assoc resp in STA context for primary link

If new link id in link switch request corresponds to assoc link,
generating of assoc resp fails as lookup of primary link id in
per-STA pro

qcacld-3.0: Use assoc resp in STA context for primary link

If new link id in link switch request corresponds to assoc link,
generating of assoc resp fails as lookup of primary link id in
per-STA profile results error.

For link switch to primary link id, use the existing assoc resp
and continue for assoc resp processing.

Change-Id: I3f88f9136962e88b51b235968ef2d9a0b79b35ad
CRs-Fixed: 3586092

show more ...

qcacld-3.0: Avoid MLO RSO start before link vdev up

For mlo initial connect, vdev0 connected first, when received assoc rsp,
then up vdev0 at last trigger vdev1 connect, set wlan_connected_links
bit

qcacld-3.0: Avoid MLO RSO start before link vdev up

For mlo initial connect, vdev0 connected first, when received assoc rsp,
then up vdev0 at last trigger vdev1 connect, set wlan_connected_links
bitmap for vdev1.

For owe 1x roaming, vdev1 link is set up on host side, when handle roam
sync, we need stop RSO first to finish EAPOL, then trigger vdev1 connect,
set wlan_connected_links bitmap for vdev1.

Above design has race condition issue:
vdev0 becomes up (T1) before set wlan_connected_links bitmap for vdev1
(T2), if enable RSO for vdev0 happens between T1 and T2 for some reason
like vdev2 connect/disconnect, mlo_check_if_all_vdev_up return true, so
mlo vdev0 RSO is enabled in F/W before vdev1 up, which is unexpected.

Fix proposal for both initial connect and roaming:
For mlo initial connect, vdev0 connected first, when received assoc rsp,
we know whether other links need set up, can set wlan_connected_links
bitmap at that time, then up vdev0, at last trigger vdev1 connect.

For owe 1x roaming, vdev1 link is set up on host side, when handle roam
sync, we need stop RSO first to finish EAPOL, then set
wlan_connected_links bitmap for vdev1, at last trigger vdev1 connect.

Change-Id: I9abe48dbf7781be80ab5ec99ec42e6324a676283
CRs-Fixed: 3576584

show more ...

qcacld-3.0: Add 11be BW 320 in GETSTAINFO

Implement changes to support 11be mode
and bandwidth 320 required for EHT.
Change-Id: I0b5e82e4d5fa0c2f1c8c8921d2b13a111582184c
CRs-Fixed: 3554106

qcacld-3.0: Fix improper arguments for QDF_MAC_ADDR_REF

Currently in driver while using QDF_MAC_ADDR_FMT to print mac
address, the mac address reference provided to QDF_MAC_ADDR_REF is
incorrect in

qcacld-3.0: Fix improper arguments for QDF_MAC_ADDR_REF

Currently in driver while using QDF_MAC_ADDR_FMT to print mac
address, the mac address reference provided to QDF_MAC_ADDR_REF is
incorrect in some cases. Fix all such instances.

Change-Id: Ib5d84b01542ebf04ee7d23fb65305036651a6a45
CRs-Fixed: 3556409

show more ...

qcacld-3.0: Remove unused structures from for set keys

Remove unused structures from wma_if.h and ani_sysytem_defs.h
for set key.

Change-Id: I68aff20694a4fc45fa61071bbc2ef4289351e9a9
CRs-Fixed: 354

qcacld-3.0: Remove unused structures from for set keys

Remove unused structures from wma_if.h and ani_sysytem_defs.h
for set key.

Change-Id: I68aff20694a4fc45fa61071bbc2ef4289351e9a9
CRs-Fixed: 3549004

show more ...

qcacld-3.0: Add additional bazel-related changes

Add additional bazel-related changes to resolve build errors.

Change-Id: I891556a81d217fded38915293aeea83a389d6782
CRs-Fixed: 3517415

qcacld-3.0: Fix low TPC power for vendor DTPC IE

Currently low TPC power is configured to firmware if power constraint IE
is not present and only vendor DTPC IE is present.
TPC power calculation is

qcacld-3.0: Fix low TPC power for vendor DTPC IE

Currently low TPC power is configured to firmware if power constraint IE
is not present and only vendor DTPC IE is present.
TPC power calculation is depends on regulatory power, ap power constraint
and TPE IE.

To fix this add new check is_power_constraint_abs in reg_tpc_obj.
Whenever local power constraint is from DTPC IE, is_power_constraint_abs
is set to true. And TPC power is calculated with regulatory power,
DTPC IE power and TPE IE power.

Change-Id: I37b14d144242fa30f02268f8a76b1b016bf69848
CRs-Fixed: 3383531

show more ...

qcacld-3.0: Configure listen interval in assoc request

Populate the user-defined listen interval in association
request frame for STA.

Change-Id: I1733ed1d528fa99fc5556639ddfbd68ca97a40e0
CRs-Fixed

qcacld-3.0: Configure listen interval in assoc request

Populate the user-defined listen interval in association
request frame for STA.

Change-Id: I1733ed1d528fa99fc5556639ddfbd68ca97a40e0
CRs-Fixed: 3438369

show more ...

qcacld-3.0: Find best 6 GHz power type for connection

Find the best 6 GHz power type for connection
according to following regulatory policy:
1) SP power type is selected only if AP advertises
SP

qcacld-3.0: Find best 6 GHz power type for connection

Find the best 6 GHz power type for connection
according to following regulatory policy:
1) SP power type is selected only if AP advertises
SP and client supports SP.
2) LPI power type is selected only if AP advertises
LPI and client supports LPI.
3) VLP power type is selected for the below cases,
a) AP advertises VLP and client supports VLP
b) AP advertises SP but client doesn't support
SP but supports VLP.
c) AP advertises LPI but client doesn't support
LPI but supports VLP.

Change-Id: I582fb582e1e11b731a1c6cda01f4fc366f166143
CRs-Fixed: 3456192

show more ...

qcacld-3.0: Remove obsolete tAniSirLim counters

The tAniSirLim struct contains multiple counters. Although all of them
are initialized, only some of them are ever incremented, and very few
of them a

qcacld-3.0: Remove obsolete tAniSirLim counters

The tAniSirLim struct contains multiple counters. Although all of them
are initialized, only some of them are ever incremented, and very few
of them actually have their values read. Since it is pointless to keep
counters that are never examined, remove the ones that are never read.

As part of the cleanup replace the tAniSirLim typedef with a properly
named struct to align with the coding standard.

Change-Id: I8b306ff9ae92a54953dd54b80c58e691612c43a0
CRs-Fixed: 3424936

show more ...

qcacld-3.0: Fill proper RSSI value during kickout/bmiss

Issue: Host reports different RSSI values during roaming
trigger logging and subsequent deauth TX logging to user
space.

In case of roam trig

qcacld-3.0: Fill proper RSSI value during kickout/bmiss

Issue: Host reports different RSSI values during roaming
trigger logging and subsequent deauth TX logging to user
space.

In case of roam trigger roaming, driver sends the rssi value
to user space from wmi_roam_ap_info tlv in roam scan results.

In case of disconnection due to BMISS or STA KICKOUT case,
host does not receive latest beacon from FW. This results,
on disconnection, host reports deauth TX logs to userspace
using old RSSI present in mac->lim.bss_rssi which is updated
when beacon or probe response is received in host.

Fix is to update mac->lim.bss_rssi while processing sta
kickout or bmiss event coming from FW.

Change-Id: I108f94959fbf915d8f67f443a9fcd54d595c27d1
CRs-Fixed: 3417363

show more ...

qcacld-3.0: Enhance logic to support mlo 2+ links

Enhance the code logic to support mlo 2+ links.

Change-Id: I618d789a502f0577d62d62243a25e7324e685315
CRs-Fixed: 3193628