From c9e9eb92915126eecb9014929407c87a5b2cfb8d Mon Sep 17 00:00:00 2001 From: Mukul Sharma Date: Thu, 20 Oct 2016 15:36:20 +0530 Subject: qcacld-3.0: Do not handle regdomain notifier after cfg80211 suspend qcacld-2.0 to qcacld-3.0 propagation Currently, kernel invoke the regdomain notifier to host driver using registered callback. If kernel call this callback after cfg80211 aka system suspend, Then because of race condition host might send the PDEV SET REGDOMAIN/PARAM to fwr after WOW ENABLE cmd which is not correct cmd sequence. Change-Id: Ie3cd94d86345c9b6de0c5597d23e0b0dc6751937 CRs-Fixed: 1075079 --- core/hdd/src/wlan_hdd_regulatory.c | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/core/hdd/src/wlan_hdd_regulatory.c b/core/hdd/src/wlan_hdd_regulatory.c index 86850c6bbfe9..666bc778e6fc 100644 --- a/core/hdd/src/wlan_hdd_regulatory.c +++ b/core/hdd/src/wlan_hdd_regulatory.c @@ -629,6 +629,11 @@ void hdd_reg_notifier(struct wiphy *wiphy, return; } + if (hdd_ctx->isWiphySuspended == true) { + hdd_err("%s: system/cfg80211 is already suspend", __func__); + return; + } + if (('K' == request->alpha2[0]) && ('R' == request->alpha2[1])) request->dfs_region = DFS_KR_REGION; -- cgit v1.2.3