From: Wey-Yi Guy <wey-yi.w.guy@xxxxxxxxx>
In current implementation, mac80211 send dtim_period update to driver
during association, but if no NetworkManager or similar application
perform scan operation, plus tim_ie is not part of probe response; mac80211 will
not get beacon with dtim information later, then mac80211 will not pass the
information to driver for update.
Call ieee80211_hw_config() with IEEE80211_CONF_CHANGE_PS flag set to
allow driver make correct dtim adjustment if dtim_period change
detected. Also perform recalc_ps operation if needed.
Signed-off-by: Wey-Yi Guy <wey-yi.w.guy@xxxxxxxxx>
---
v2: move the function to ieee80211_rx_bss_info() to make sure only call
when needed
v3: do not check for STATION and call recal_ps to perform hw_config
---
net/mac80211/mlme.c | 19 ++++++++++++++++++-
1 files changed, 18 insertions(+), 1 deletions(-)
diff --git a/net/mac80211/mlme.c b/net/mac80211/mlme.c
index 1e1d16c..46df5bf 100644
--- a/net/mac80211/mlme.c
+++ b/net/mac80211/mlme.c
@@ -1157,6 +1157,21 @@ static bool ieee80211_assoc_success(struct ieee80211_work *wk,
}
+static void ieee80211_update_dtim(struct ieee80211_sub_if_data *sdata,
+ struct ieee80211_local *local,
+ struct ieee80211_bss *bss)
+{
+ if (!(local->hw.flags & IEEE80211_HW_SUPPORTS_PS))
+ return;
+
+ if (sdata->vif.bss_conf.dtim_period != bss->dtim_period) {
+ sdata->vif.bss_conf.dtim_period = bss->dtim_period;
+ mutex_lock(&local->iflist_mtx);
+ ieee80211_recalc_ps(local, -1);
+ mutex_unlock(&local->iflist_mtx);
+ }
+}
+
static void ieee80211_rx_bss_info(struct ieee80211_sub_if_data *sdata,
struct ieee80211_mgmt *mgmt,
size_t len,
@@ -1181,8 +1196,10 @@ static void ieee80211_rx_bss_info(struct ieee80211_sub_if_data *sdata,
bss = ieee80211_bss_info_update(local, rx_status, mgmt, len, elems,
channel, beacon);
- if (bss)
+ if (bss) {
ieee80211_rx_bss_put(local, bss);
+ ieee80211_update_dtim(sdata, local, bss);
+ }
if (!sdata->u.mgd.associated)
return;
--
1.5.6.3
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
