samsung-sm8650/android_kernel_samsung_sm8650-modules
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

qcacld-3.0: Avoid repeated BTM connectivity log in full scan case

Browse Source 
In the api cm_roam_btm_req_event(), BTM request and
BTM Candidate Connectivity logs are printed for both
partial and full scan when disassoc_imminent is set for BTM
roam trigger. But actually, over the air frame was received
only once on the device.

So to avoid BTM frame logs duplication,
ignore the BTM request frame TLV & btm candidate TLV received from
firmware after BTM roam trigger with disassoc imminent set.

Change-Id: I7d8cf4a4f0c7e2ee7958ae3fc309f14890c2fd33
CRs-Fixed: 3675909
This commit is contained in:
Vijay Raj
2023-12-04 04:44:12 -08:00
committed by Ravindra Konda
parent 3bf9181471
commit 24da60d78f
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
components/umac/mlme/connection_mgr/core/src/wlan_cm_roam_offload.c
View File

@@ -7041,6 +7041,16 @@ cm_roam_btm_req_event(struct wmi_roam_btm_trigger_data *btm_data,
qdf_mem_zero(&wlan_diag_event, sizeof(wlan_diag_event));
/* The BTM req and BTM candidate event is logged twice
* for both partial and full scan but the OTA frame is received
* is received only once on the device. Restricting the
* BTM req and BTM candidate event to be logged only for partial scan
*/
if (trigger_info->present &&
trigger_info->scan_type == ROAM_STATS_SCAN_TYPE_FULL &&
btm_data->disassoc_timer)
return status;
populate_diag_cmn(&wlan_diag_event.diag_cmn, vdev_id,
(uint64_t)btm_data->timestamp,
NULL);