From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
"linville@tuxdriver.com" <linville@tuxdriver.com>,
"kalle.valo@iki.fi" <kalle.valo@iki.fi>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"j@w1.fi" <j@w1.fi>,
"buytenh@wantstofly.org" <buytenh@wantstofly.org>
Subject: Re: [PATCH] mac80211: wait for beacon before enabling powersave
Date: Wed, 27 Jan 2010 10:14:22 -0800 [thread overview]
Message-ID: <1264616062.8619.22.camel@wwguy-ubuntu> (raw)
In-Reply-To: <43e72e891001271014j667221bqa11d56f3a68f6099@mail.gmail.com>
On Wed, 2010-01-27 at 10:14 -0800, Luis R. Rodriguez wrote:
> On Wed, Jan 27, 2010 at 10:04 AM, Guy, Wey-Yi <wey-yi.w.guy@intel.com> wrote:
> > On Wed, 2010-01-27 at 10:01 -0800, Luis R. Rodriguez wrote:
> >> On Tue, Jan 26, 2010 at 5:19 AM, Johannes Berg
> >> <johannes@sipsolutions.net> wrote:
> >> > Because DTIM information is required for powersave
> >> > but is only conveyed in beacons, wait for a beacon
> >> > before enabling powersave, and change the way the
> >> > information is conveyed to the driver accordingly.
> >> >
> >> > mwl8k doesn't currently seem to implement PS but
> >> > requires the DTIM period in a different way; after
> >> > talking to Lennert we agreed to just have mwl8k do
> >> > the parsing itself in the finalize_join work.
> >>
> >> Not sure if this is merged yet. If not it might be good to add to the
> >> commit log a brief about the impact of the fix for distribution
> >> purposes looking to cherry pick some fixes that may cure some issues.
> >>
> >> The impact of this fix is that the DTIM settings of > 1 would now be
> >> respected in the odd situation a beacon would not be received prior to
> >> association. Ensuring we use a higher DTIM would mean saving more
> >> power as it would mean we can sleep longer.
> >>
> >> This is not propagated to stable but if it turns out this can enhance
> >> power save since DTIM might usually be > 1 and the race may be more
> >> common than we expected we may need a respective stable solution.
> >>
> >
> > It will be nice to see a respective solution for stable since this
> > impact power save which is very important for certain platform.
>
> Well how about your patch for stable then?
>
if ok with you and Johannes, I will like to see it happen, the only
issue is, my patch only address iwlwifi but not mwl8k.
next prev parent reply other threads:[~2010-01-27 18:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 13:19 [PATCH] mac80211: wait for beacon before enabling powersave Johannes Berg
2010-01-26 16:41 ` Lennert Buytenhek
2010-01-27 7:54 ` Kalle Valo
2010-01-27 18:01 ` Luis R. Rodriguez
2010-01-27 18:04 ` Guy, Wey-Yi
2010-01-27 18:14 ` Luis R. Rodriguez
2010-01-27 18:14 ` Guy, Wey-Yi [this message]
2010-01-27 18:25 ` Luis R. Rodriguez
2010-01-27 18:59 ` Guy, Wey-Yi
2010-01-27 19:13 ` Luis R. Rodriguez
2010-01-28 9:51 ` Lennert Buytenhek
2010-01-27 19:13 ` Johannes Berg
2010-01-27 19:44 ` John W. Linville
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=1264616062.8619.22.camel@wwguy-ubuntu \
--to=wey-yi.w.guy@intel.com \
--cc=buytenh@wantstofly.org \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=kalle.valo@iki.fi \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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).