qcacld-3.0: Modify Roam result log for MLO connection

For Roam result connectivity logging, bssid is not
printed for No ROAM case when connected to a MLO AP.

Expected Log when connected to MLO AP:
[Kernel Timestamp][ROAM] RESULT NO_ROAM
bssid=??:??:??:??:??:?? [Vendor Extra data]

Observed log when connected to a MLO AP:
[Kernel Timestamp][ROAM] RESULT NO_ROAM [Vendor Extra data]

Add "is_mlo" parameter to be sent in order indicate
userspace the whether the log belongs to MLO AP.
Modify BSSID to bss peer mac of assoc link to be
printed as part Roam Result No roam log when
connected to a MLO AP

Change-Id: Ia9acc1cf7c5377b595771f2718edd9dbf8f45367
CRs-Fixed: 3638160
This commit is contained in:
Vijay Raj
2023-10-13 09:43:27 -07:00
committed by Ravindra Konda
parent 8653d961c9
commit 72a9394643
2 changed files with 61 additions and 2 deletions

View File

@@ -597,6 +597,7 @@ struct wlan_diag_roam_scan_done {
* @diag_cmn: Common diag info
* @version: Structure Version
* @is_roam_successful: True if roamed successfully or false if roaming failed
* @is_mlo: Indicates whether the current connection is a MLO connection
* @reserved: Reserved
* @roam_fail_reason: Roam failure reason code defined in enum
* wlan_roam_failure_reason_code
@@ -605,7 +606,8 @@ struct wlan_diag_roam_result {
struct wlan_connectivity_log_diag_cmn diag_cmn;
uint8_t version;
uint8_t is_roam_successful:1;
uint8_t reserved:7;
uint8_t is_mlo:1;
uint8_t reserved:6;
uint16_t roam_fail_reason;
} qdf_packed;