wifi: iwlwifi: mvm: don't check dtim_period in new API
In newer firmware APIs the firmware is responsible for tracking the DTIM period and other beacon timing, so we don't need to wait with setting associated. In real MLO operation, mac80211 isn't tracking this anyway, and connections wouldn't work. Signed-off-by: Johannes Berg <johannes.berg@intel.com> Signed-off-by: Gregory Greenman <gregory.greenman@intel.com> Link: https://lore.kernel.org/r/20230328104949.02354241fede.Id957bed3851fdf1fe902d79a1b0338c6d80bc0e1@changeid Signed-off-by: Johannes Berg <johannes.berg@intel.com>
This commit is contained in:
parent
1a3e70391e
commit
ac251da91a
@ -102,9 +102,7 @@ static int iwl_mvm_mld_mac_ctxt_cmd_sta(struct iwl_mvm *mvm,
|
||||
cmd.client.ctwin =
|
||||
iwl_mvm_mac_ctxt_cmd_p2p_sta_get_oppps_ctwin(mvm, vif);
|
||||
|
||||
/* FIXME: assume for now that DTIM period is the same for all links */
|
||||
if (vif->cfg.assoc && vif->bss_conf.dtim_period &&
|
||||
!force_assoc_off) {
|
||||
if (vif->cfg.assoc && !force_assoc_off) {
|
||||
struct iwl_mvm_vif *mvmvif = iwl_mvm_vif_from_mac80211(vif);
|
||||
|
||||
cmd.client.is_assoc = cpu_to_le32(1);
|
||||
|
Loading…
x
Reference in New Issue
Block a user