From: Kalle Valo <kalle.valo@iki.fi>
To: linux-wireless@vger.kernel.org
Cc: johannes@sipsolutions.net, a.young.jason@gmail.com
Subject: [RFC PATCH v5 0/7] mac80211 client U-APSD support
Date: Thu, 31 Dec 2009 15:37:05 +0200 [thread overview]
Message-ID: <20091231133626.29899.95683.stgit@tikku> (raw)
Hello,
here is my proposal how to add U-APSD client support to mac80211. I
also included example driver implementation for wl1251.
Please comment. Also I would like to get comments how U-APSD needs to
be implemented in different hardware.
v5:
o rename IEEE80211_HW_UAPSD to IEEE80211_HW_SUPPORTS_UAPSD
o U-APSD queue and max SP length configuration debugfs interface
(requested by Jason)
o dynamic ps support for U-APSD
o by default enable U-APSD in all queues
o back to RFC state due to new code
o add a warning if both PS_NULLFUNC_STACK and U-APSD are enabled
o wl1251: set qos null data template
o more defines to ieee80211.h
v4:
o use IEEE80211_WMM_IE_STA_QOSINFO prefix in ieee80211.h (Jason Young)
o fix VI and BK qosinfo values in ieee80211.h (Jason Young)
o add IEEE80211_WMM_IE_AP_QOSINFO_UAPSD
v3:
o remove unnecessary debugfs interface, people can recompile mac80211
in case they want to try enable more queues
o add max SP length defines to ieee80211.h
o removed unnecessary code comments
v2:
o remove cfg80211 changes
o rename IEEE80211_QOS_IE to IEEE80211_WMM_IE_STA in ieee80211.h
---
Kalle Valo (7):
mac80211: add U-APSD client support
mac80211: add debugfs interface for U-APSD queue configuration
mac80211: create tx handler for dynamic ps
mac80211: check uapsd state for dynamic power save
ieee80211: add struct ieee80211_hdr_qos
wl1251: create qos null data template
wl1251: add U-APSD support
drivers/net/wireless/wl12xx/wl1251_main.c | 37 +++++++++-
include/linux/ieee80211.h | 27 +++++++
include/net/mac80211.h | 7 ++
net/mac80211/cfg.c | 7 ++
net/mac80211/debugfs.c | 94 ++++++++++++++++++++++++++
net/mac80211/ieee80211_i.h | 24 ++++++-
net/mac80211/main.c | 6 ++
net/mac80211/mlme.c | 31 ++++++++
net/mac80211/scan.c | 18 +++++
net/mac80211/tx.c | 106 ++++++++++++++++++-----------
net/mac80211/util.c | 2 +
net/mac80211/work.c | 11 ++-
12 files changed, 321 insertions(+), 49 deletions(-)
next reply other threads:[~2009-12-31 13:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-31 13:37 Kalle Valo [this message]
2009-12-31 13:37 ` [RFC PATCH v5 1/7] mac80211: add U-APSD client support Kalle Valo
2009-12-31 13:37 ` [RFC PATCH v5 2/7] mac80211: add debugfs interface for U-APSD queue configuration Kalle Valo
2010-01-05 9:48 ` Johannes Berg
2010-01-05 10:27 ` Kalle Valo
2010-01-05 10:44 ` Johannes Berg
2010-01-05 10:53 ` Kalle Valo
2009-12-31 13:37 ` [RFC PATCH v5 3/7] mac80211: create tx handler for dynamic ps Kalle Valo
2009-12-31 13:37 ` [RFC PATCH v5 4/7] mac80211: check uapsd state for dynamic power save Kalle Valo
2009-12-31 13:37 ` [RFC PATCH v5 5/7] ieee80211: add struct ieee80211_hdr_qos Kalle Valo
2009-12-31 13:37 ` [RFC PATCH v5 6/7] wl1251: create qos null data template Kalle Valo
2009-12-31 13:37 ` [RFC PATCH v5 7/7] wl1251: add U-APSD support Kalle Valo
2010-01-05 9:51 ` [RFC PATCH v5 0/7] mac80211 client " Johannes Berg
2010-01-05 10:31 ` Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091231133626.29899.95683.stgit@tikku \
--to=kalle.valo@iki.fi \
--cc=a.young.jason@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).