qcacld-3.0: Fix STA disconnect when SAP detected radar
Sap is started on freq 5640Mhz with BW 160Mhz and radar event generated, and then SAP moves to freq 5680Mhz. But before the move done, the regdomain update (because of Radar detection) will trigger the wlansap_get_chan_band_restrict to run and further move to SAP to freq 5180Mhz. The client side still get old CSA event with 5680Mhz, and switch to 5680Mhz and get Bmiss finally because actually SAP is moved to 5180Mhz. The band restrict logic should not handle radar disabled channel. The radar detected channel (in NOL) should be handled by SAP radar channel switch logic only. Fix by skip the band strict check if disabled channel is in NOL list, let the SAP radar logic to handle channel switch. Change-Id: Ic284cf48653d7ebf8bc37a33d6caf1a5e673b78e CRs-Fixed: 3019950
This commit is contained in:

committed by
Madan Koyyalamudi

父節點
ac66479f44
當前提交
71a336905d
@@ -3209,7 +3209,8 @@ qdf_freq_t wlansap_get_chan_band_restrict(struct sap_context *sap_ctx,
|
||||
restart_freq, restart_ch_width);
|
||||
*csa_reason = CSA_REASON_BAND_RESTRICTED;
|
||||
} else if (wlan_reg_is_disable_for_freq(mac->pdev,
|
||||
sap_ctx->chan_freq)) {
|
||||
sap_ctx->chan_freq) &&
|
||||
!utils_dfs_is_freq_in_nol(mac->pdev, sap_ctx->chan_freq)) {
|
||||
sap_debug("channel is disabled");
|
||||
*csa_reason = CSA_REASON_CHAN_DISABLED;
|
||||
return wlansap_get_safe_channel_from_pcl_and_acs_range(sap_ctx);
|
||||
|
Reference in New Issue
Block a user