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>
This commit is contained in:
parent
82cad2a0b0
commit
908628db14
|
@ -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);
|
||||
|
|
Loading…
Reference in New Issue