diff options
| author | Manikandan Mohan <manikand@qca.qualcomm.com> | 2015-04-18 12:39:34 -0700 |
|---|---|---|
| committer | Akash Patel <c_akashp@qca.qualcomm.com> | 2015-04-18 15:37:09 -0700 |
| commit | ba996cdc201589bee284255ee574d2ee6952619f (patch) | |
| tree | 2dba292e4814c515be0c0054ad0a54177e51f816 | |
| parent | b2763acd085b2c345f4a6120bdee43a7eccbfc60 (diff) | |
qcacld: Fix SAP DFS channel DHCP issue due to IPA
Fix an issue where IPA module sends failure when we get second
start_bss event for SAP operating in DFS channel after CAC. This
results in SAP stopbss and client assoc failure. So check SAP
operating channel for DFS channel for second start bss event.
Change-Id: If74e66551dfa2f1bcf31750431344881017244db
CRs-fixed: 824513
| -rw-r--r-- | CORE/HDD/src/wlan_hdd_ipa.c | 16 |
1 files changed, 12 insertions, 4 deletions
diff --git a/CORE/HDD/src/wlan_hdd_ipa.c b/CORE/HDD/src/wlan_hdd_ipa.c index a3d5f0c60ba6..f5c72ef0b35a 100644 --- a/CORE/HDD/src/wlan_hdd_ipa.c +++ b/CORE/HDD/src/wlan_hdd_ipa.c @@ -3404,10 +3404,18 @@ int hdd_ipa_wlan_evt(hdd_adapter_t *adapter, uint8_t sta_id, case WLAN_AP_CONNECT: if (adapter->ipa_context) { - HDD_IPA_LOG(VOS_TRACE_LEVEL_INFO, - "%s: Evt: %d, SAP already connected", - msg_ex->name, meta.msg_type); - return -EINVAL; + /* For DFS channel we get two start_bss event before + * and after CAC, so dont return error. + */ + if(VOS_IS_DFS_CH( + adapter->sessionCtx.ap.operatingChannel)) { + return 0; + } else { + HDD_IPA_LOG(VOS_TRACE_LEVEL_INFO, + "%s: Evt: %d, SAP already connected", + msg_ex->name, meta.msg_type); + return -EINVAL; + } } #ifdef IPA_UC_OFFLOAD |
