Commits #5 and #6 cover the basic subset of functions, that each mesh node
must support to communicate in the presence of power saving nodes.
The current patchset does not implement any actual power savings yet (no
hardware configuration, no doze state).
Mesh powersave is different from client mode powersave in the sense that
1) there is not just a singular power mode towards the access point, but a
link-specific power mode towards each peer instead
2) peers also maintain a power mode towards us (the local STA)
3) each node has to buffer frames towards power saving neighbors
changes since PATCHv1:
- explicitly clear QoS control field in mps_qos_null_get
- beautify FILL_IN_MESH_PARAM_IF_SET macro
Marco Porsch (6):
nl80211: add range checks to mesh parameters
mac80211: update mesh peer link counter during userspace peering
mac80211: move add_tim to subfunction
{cfg,nl,mac}80211: set beacon interval and DTIM period on mesh join
{cfg,nl}80211: mesh power mode primitives and userspace access
mac80211: mesh power save basics
include/linux/ieee80211.h | 17 ++
include/net/cfg80211.h | 25 ++
include/uapi/linux/nl80211.h | 47 +++
net/mac80211/Kconfig | 11 +
net/mac80211/Makefile | 3 +-
net/mac80211/cfg.c | 54 +++-
net/mac80211/debug.h | 10 +
net/mac80211/debugfs_netdev.c | 5 +
net/mac80211/debugfs_sta.c | 5 +-
net/mac80211/ieee80211_i.h | 7 +
net/mac80211/mesh.c | 37 ++-
net/mac80211/mesh.h | 35 ++-
net/mac80211/mesh_hwmp.c | 7 +
net/mac80211/mesh_pathtbl.c | 1 +
net/mac80211/mesh_plink.c | 35 ++-
net/mac80211/mesh_ps.c | 640 +++++++++++++++++++++++++++++++++++++++++
net/mac80211/rx.c | 7 +
net/mac80211/sta_info.c | 18 +-
net/mac80211/sta_info.h | 17 ++
net/mac80211/status.c | 5 +
net/mac80211/tx.c | 81 ++++--
net/mac80211/util.c | 4 +
net/mac80211/wme.c | 13 +-
net/wireless/mesh.c | 8 +
net/wireless/nl80211.c | 137 ++++++---
25 files changed, 1137 insertions(+), 92 deletions(-)
create mode 100644 net/mac80211/mesh_ps.c
--
1.7.9.5
--
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
