qcacld-3.0: fix regression for STA PNO WoW
qcacld-2.0 to qcacld-3.0 propagation This is to fix the regression in the case of suspend request. Below patch overkills the case for PNO and extscan in progress. Commit Subject: "Fix the PNO WoW is not configured in concurrency case" change id: I97084cfde73025f0d09b60616959c9530ba82c80 The combined condition check should be maintained to check the case for PNO or extscan in progress, otherwise the WoW would be enabled in the case PNO in progress is not enabled, and end up not setting PNO patterns and failed to reconnect after resume. Change-Id: Icc5f19d07abea9fb25479452ce1c467d7811317c CRs-fixed: 953257
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
/*
|
||||
* Copyright (c) 2013-2015 The Linux Foundation. All rights reserved.
|
||||
* Copyright (c) 2013-2016 The Linux Foundation. All rights reserved.
|
||||
*
|
||||
* Previously licensed under the ISC license by Qualcomm Atheros, Inc.
|
||||
*
|
||||
@@ -3965,7 +3965,7 @@ CDF_STATUS wma_suspend_req(tp_wma_handle wma, tpSirWlanSuspendParam info)
|
||||
i, wma->wow.gtk_err_enable[i], wma->wow.gtk_pdev_enable);
|
||||
}
|
||||
|
||||
if (!enable_wow) {
|
||||
if (!enable_wow && !pno_in_progress && !extscan_in_progress) {
|
||||
WMA_LOGD("All vdev are in disconnected state and pno/extscan is not in progress, skipping wow");
|
||||
cdf_mem_free(info);
|
||||
goto send_ready_to_suspend;
|
||||
|
Reference in New Issue
Block a user