From 24da60d78f68b6598eff8aac9614ae6270f29449 Mon Sep 17 00:00:00 2001 From: Vijay Raj Date: Mon, 4 Dec 2023 04:44:12 -0800 Subject: [PATCH] qcacld-3.0: Avoid repeated BTM connectivity log in full scan case 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 --- .../connection_mgr/core/src/wlan_cm_roam_offload.c | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/components/umac/mlme/connection_mgr/core/src/wlan_cm_roam_offload.c b/components/umac/mlme/connection_mgr/core/src/wlan_cm_roam_offload.c index e54a76e888..ab807066b2 100644 --- a/components/umac/mlme/connection_mgr/core/src/wlan_cm_roam_offload.c +++ b/components/umac/mlme/connection_mgr/core/src/wlan_cm_roam_offload.c @@ -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);