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

qcacld-3.0: Handle sap restart after opportunistic timer start failure

Browse Source 
Currently, If hadware is not dbs capable opportunistic timer
can not be started. In function if_mgr_connect_complete
policy_mgr_check_n_start_opportunistic_timer fails to start
opportunistic timer in case of non-dbs hw and sap restart
doesn't happen.

Fix is not to validate status returned by
policy_mgr_check_n_start_opportunistic_timer to restart sap
in case of non-dbs hardware.

Change-Id: I3308a5c10341950d51419907cc767c09f967b7b1
CRs-Fixed: 2792764
This commit is contained in:
sheenam monga
2020-10-09 13:23:44 +05:30
committed by snandini
parent b415eec586
commit fe95170ec6
1 changed files with 1 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
components/cmn_services/interface_mgr/src/wlan_if_mgr_sta.c
View File

@@ -120,11 +120,7 @@ QDF_STATUS if_mgr_connect_complete(struct wlan_objmgr_vdev *vdev,
if_mgr_enable_roaming(vdev, pdev, RSO_CONNECT_START); if_mgr_enable_roaming(vdev, pdev, RSO_CONNECT_START);
} }
status = policy_mgr_check_n_start_opportunistic_timer(psoc); policy_mgr_check_n_start_opportunistic_timer(psoc);
if (status) {
ifmgr_err("Failed to start dbs opportunistic timer");
return status;
}
policy_mgr_check_concurrent_intf_and_restart_sap(psoc); policy_mgr_check_concurrent_intf_and_restart_sap(psoc);