A-Team_Digital_Solutions/android_kernel_motorola_sm6375
Watch
2
0
Fork
You've already forked android_kernel_motorola_sm6375
 0
mirror of https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git synced 2026-10-09 21:59:12 -04:00
Code Issues Projects Releases Packages Wiki Activity

qcacld-3.0: Checking assoc state for bw timer when resuming

Browse source 
In runtime resuming, there is no necessary to start bw timer
if adapter is in non-assoc state.
If bw timer has been started in idle state, there will be no
match bw timer stop. In hdd_bus_bandwidth_deinit, it will consider
as abnormal.

Change-Id: Id36af395269ebf3a09429b2606dbd438f147f24f
CRs-Fixed: 2678835
This commit is contained in:
Jingxiang Ge 2020-05-06 15:51:50 +08:00 • committed by nshrivas
commit 69a3183113
2 changed files with 5 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
core/hdd/src/wlan_hdd_driver_ops.c
View file

@ -1423,7 +1423,7 @@ static int wlan_hdd_runtime_resume(struct device *dev)
hdd_err("PMO Runtime resume failed: %d", status);
} else {
if (policy_mgr_get_connection_count(hdd_ctx->psoc))
hdd_bus_bw_compute_timer_start(hdd_ctx);
hdd_bus_bw_compute_timer_try_start(hdd_ctx);
}
hdd_debug("Runtime resume done");

4
core/hdd/src/wlan_hdd_main.c
View file

@ -9329,7 +9329,11 @@ void hdd_bus_bandwidth_deinit(struct hdd_context *hdd_ctx)
{
hdd_enter();
/* it is expecting the timer has been stopped or not started
* when coming deinit.
*/
QDF_BUG(!qdf_periodic_work_stop_sync(&hdd_ctx->bus_bw_work));
qdf_periodic_work_destroy(&hdd_ctx->bus_bw_work);
qdf_spinlock_destroy(&hdd_ctx->bus_bw_lock);
hdd_pm_qos_remove_request(hdd_ctx);