wcn36xx: Update dtim period before starting BSS

The dtim period sent to FW was 0 because the dtim period
was never set. This caused an incorrect dtim count to be sent in
beacons.

Signed-off-by: Pontus Fuchs <pontus.fuchs@gmail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>

diff --git a/drivers/net/wireless/ath/wcn36xx/main.c b/drivers/net/wireless/ath/wcn36xx/main.c
index dca21ee69a6212322796da3abff28a7d924afa34..4ab5370ab7a6ff5df3d5e4b1525b7f852cc55cb6 100644 (file)
--- a/drivers/net/wireless/ath/wcn36xx/main.c
+++ b/drivers/net/wireless/ath/wcn36xx/main.c
@@ -708,6 +708,7 @@ static void wcn36xx_bss_info_changed(struct ieee80211_hw *hw,
                            bss_conf->enable_beacon);
 
                if (bss_conf->enable_beacon) {
+                       vif_priv->dtim_period = bss_conf->dtim_period;
                        vif_priv->bss_index = 0xff;
                        wcn36xx_smd_config_bss(wcn, vif, NULL,
                                               vif->addr, false);