After a disassociated event we need to make sure we reset the operational channel so that subsequent channel scans will not exclude the channel we were using. Doing a software scan on a wcn3680 showed that if we disassociated from an AP we would never see it re-appear in a scan - unless we shifted the AP to a different channel. Setting the operational channel to zero on disassociation ensures that this situation will not arise in the wild. Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@xxxxxxxxxx> --- drivers/net/wireless/ath/wcn36xx/main.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/wireless/ath/wcn36xx/main.c b/drivers/net/wireless/ath/wcn36xx/main.c index fb8978a3c11e..4681d085b683 100644 --- a/drivers/net/wireless/ath/wcn36xx/main.c +++ b/drivers/net/wireless/ath/wcn36xx/main.c @@ -908,6 +908,7 @@ static void wcn36xx_bss_info_changed(struct ieee80211_hw *hw, bss_conf->bssid, vif->addr, WCN36XX_HAL_LINK_IDLE_STATE); + wcn36xx_smd_switch_channel(wcn, vif, 0); } } -- 2.27.0
