From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Kalle Valo <kalle.valo@nokia.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC 2/2] mac80211: implement dynamic power save
Date: Mon, 10 Nov 2008 12:14:44 -0800 [thread overview]
Message-ID: <20081110201444.GI6918@tesla> (raw)
In-Reply-To: <1226245439-30329-3-git-send-email-kalle.valo@nokia.com>
On Sun, Nov 09, 2008 at 07:43:59AM -0800, Kalle Valo wrote:
> Enable power save only after an idle transmit timeout. The timeout can
> be enabled with:
>
> iwconfig wlan0 power timeout 500m
>
> Thanks to Johannes Berg for the help with the design.
>
> Signed-off-by: Kalle Valo <kalle.valo@nokia.com>
> ---
> net/mac80211/ieee80211_i.h | 9 +++++++++
> net/mac80211/main.c | 5 +++++
> net/mac80211/mlme.c | 43 +++++++++++++++++++++++++++++++++++++++++--
> net/mac80211/tx.c | 18 ++++++++++++++++++
> net/mac80211/wext.c | 8 ++++++--
> 5 files changed, 79 insertions(+), 4 deletions(-)
>
> diff --git a/net/mac80211/ieee80211_i.h b/net/mac80211/ieee80211_i.h
> index 3f25955..ab0e2df 100644
> --- a/net/mac80211/ieee80211_i.h
> +++ b/net/mac80211/ieee80211_i.h
> @@ -688,7 +688,12 @@ struct ieee80211_local {
> */
> int wifi_wme_noack_test;
> unsigned int wmm_acm; /* bit field of ACM bits (BIT(802.1D tag)) */
> +
> bool powersave;
> + int dynamic_ps_timeout;
> + struct work_struct ps_enable_work;
> + struct work_struct ps_disable_work;
> + struct timer_list dynamic_ps_timer;
>
> #ifdef CONFIG_MAC80211_DEBUGFS
> struct local_debugfsdentries {
> @@ -973,6 +978,10 @@ int ieee80211_set_freq(struct ieee80211_sub_if_data *sdata, int freq);
> u64 ieee80211_mandatory_rates(struct ieee80211_local *local,
> enum ieee80211_band band);
>
> +void ieee80211_ps_enable_work(struct work_struct *work);
> +void ieee80211_ps_disable_work(struct work_struct *work);
Should these also be prefixed with _dynamic ? May confuse other people
working on regular ps mode I think.
Also can you elaborate a bit in the patch/log as to what dynamic power save
concept is, what drivers who implement it are expected to do as well?
Thanks,
Luis
next prev parent reply other threads:[~2008-11-10 20:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-09 15:43 [RFC] mac80211 dynamic powersave Kalle Valo
2008-11-09 15:43 ` [RFC 1/2] mac80211: enable IEEE80211_CONF_PS only when associated Kalle Valo
2008-11-10 9:28 ` Johannes Berg
2008-11-10 9:36 ` Kalle Valo
2008-11-09 15:43 ` [RFC 2/2] mac80211: implement dynamic power save Kalle Valo
2008-11-10 9:36 ` Johannes Berg
2008-11-10 9:49 ` Kalle Valo
2008-11-10 9:53 ` Johannes Berg
2008-11-10 20:14 ` Luis R. Rodriguez [this message]
2008-11-11 7:14 ` Kalle Valo
2008-11-11 10:18 ` Vivek Natarajan
2008-11-11 13:09 ` Kalle Valo
2008-11-11 16:40 ` Nick Kossifidis
2008-11-11 4:32 ` [RFC] mac80211 dynamic powersave Vivek Natarajan
2008-11-11 10:38 ` Johannes Berg
2008-11-12 6:17 ` Vivek Natarajan
2008-11-12 17:33 ` Luis R. Rodriguez
[not found] ` <8e92b4100811102018q4a13568l625abf2c59dca253@mail.gmail.com>
2008-11-11 12:29 ` Kalle Valo
2008-11-11 12:57 ` Johannes Berg
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=20081110201444.GI6918@tesla \
--to=lrodriguez@atheros.com \
--cc=kalle.valo@nokia.com \
--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).