linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@nokia.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC v3 4/4] mac80211: move dynamic_ps_timeout to hw.conf
Date: Mon, 01 Dec 2008 22:30:37 +0200	[thread overview]
Message-ID: <87hc5nbpua.fsf@nokia.com> (raw)
In-Reply-To: <43e72e890812011111h53553a18x2d17c9cf267331dd@mail.gmail.com> (ext Luis R. Rodriguez's message of "Mon\, 1 Dec 2008 11\:11\:48 -0800")

Luis R. Rodriguez <mcgrof@gmail.com> writes:

> On Fri, Nov 28, 2008 at 11:49 AM, Kalle Valo <kalle.valo@nokia.com> wrote:
>
>> diff --git a/net/mac80211/wext.c b/net/mac80211/wext.c
>> index b3ee0dc..95455d0 100644
>> --- a/net/mac80211/wext.c
>> +++ b/net/mac80211/wext.c
>> @@ -962,7 +962,7 @@ static int ieee80211_ioctl_siwpower(struct net_device *dev,
>>
>>        if (wrq->disabled) {
>>                ps = false;
>> -               local->dynamic_ps_timeout = 0;
>> +               local->hw.conf.dynamic_ps_timeout = 0;
>>                goto set;
>>        }
>>
>> @@ -977,7 +977,7 @@ static int ieee80211_ioctl_siwpower(struct net_device *dev,
>>        }
>>
>>        if (wrq->flags & IW_POWER_TIMEOUT)
>> -               local->dynamic_ps_timeout = wrq->value / 1000;
>> +               local->hw.conf.dynamic_ps_timeout = wrq->value / 1000;
>>
>>        if (ps == local->powersave)
>>                return ret;
>> @@ -986,9 +986,9 @@ set:
>>        local->powersave = ps;
>>
>>        if (ifsta->flags & IEEE80211_STA_ASSOCIATED) {
>> -               if (local->dynamic_ps_timeout > 0)
>> +               if (conf->dynamic_ps_timeout > 0)
>>                        mod_timer(&local->dynamic_ps_timer, jiffies +
>> -                                 msecs_to_jiffies(local->dynamic_ps_timeout));
>> +                                 msecs_to_jiffies(conf->dynamic_ps_timeout));
>>                else {
>>                        if (local->powersave)
>>                                conf->flags |= IEEE80211_CONF_PS;
>
> Would it be too much trouble to add this via cfg80211/nl80211 instead
> or at least add both? The more we can push in that direction the
> better.

I definitely would like to see nl80211 support for power save. For
example, I think currently there's no way for the user space to know
dtim period of the bss. (If I'm wrong here, please let me know). We
definitely should fix that in nl80211 to make it easier for the user
space decide on correct power save settings.

Let's start to work on nl80211 after client power save features in
mac80211 are in better shape. At that time we also have a better
understanding of what's needed for the user space interface. Now
things are a bit sketchy still.

-- 
Kalle Valo

      parent reply	other threads:[~2008-12-01 20:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-28 19:49 [RFC v3] mac80211 dynamic power save Kalle Valo
2008-11-28 19:49 ` [RFC v3 1/4] mac80211: enable IEEE80211_CONF_PS only when associated Kalle Valo
2008-11-28 22:11   ` Johannes Berg
2008-11-29  6:50     ` Kalle Valo
2008-11-28 19:49 ` [RFC v3 2/4] mac80211: implement dynamic power save Kalle Valo
2008-11-28 22:14   ` Johannes Berg
2008-11-29  6:53     ` Kalle Valo
2008-12-01 19:10   ` Luis R. Rodriguez
2008-12-01 22:40     ` Johannes Berg
2008-12-01 23:49       ` Luis R. Rodriguez
2008-12-02 19:42     ` Kalle Valo
2008-11-28 19:49 ` [RFC v3 3/4] mac80211: add IEEE80211_HW_NO_DYNAMIC_PS flag Kalle Valo
2008-11-28 22:15   ` Johannes Berg
2008-11-29  6:55     ` Kalle Valo
2008-11-28 19:49 ` [RFC v3 4/4] mac80211: move dynamic_ps_timeout to hw.conf Kalle Valo
2008-11-28 22:18   ` Johannes Berg
2008-11-29  7:00     ` Kalle Valo
2008-12-01 19:11   ` Luis R. Rodriguez
2008-12-01 19:41     ` Johannes Berg
2008-12-01 20:36       ` Luis R. Rodriguez
2008-12-01 20:30     ` Kalle Valo [this message]

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=87hc5nbpua.fsf@nokia.com \
    --to=kalle.valo@nokia.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    /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).