Vijay Raj 6b467392ce qcacld-3.0: Add band check to differentiate between AP types during roaming ... In the api cm_roam_mgmt_frame_event(), the received frame info is differentiated between legacy and MLO AP on the basis whether the current vdev is a ML vdev or not. This results in undesired logging of result during MLo to legacy AP roam failure case as the vdev is still the ML vdev as it is maintaining the current connection with the ML AP while the frame info data received from FW is for legacy AP. Add a band check when processing the roam frame info data received from the FW as band info in roam frame data follows the following format: 1. 0: if the FW tried to roam to a legacy AP 2. when tried to a MLO AP, it will represent the link it forms association. The format as follows: * BIT 0: When it is associated on 2 GHz link * BIT 1: When it is associated on 5 GHz link * BIT 2: when it is associated on 6 GHz link Change-Id: I7854ef368776ba11d4cdc8aca28ac86c8c2f4efa CRs-Fixed: 3866223		2024-07-24 00:58:13 -07:00
..
interface_mgr	qcacld-3.0: initialize structure parameters before use	2024-05-14 05:02:52 -07:00
logging	qcacld-3.0: Add band check to differentiate between AP types during roaming	2024-07-24 00:58:13 -07:00
policy_mgr	qcacld-3.0: fix compilation failures caused by type mismatch	2024-07-02 09:51:14 -07:00