From: Johannes Berg <johannes@sipsolutions.net>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
Stanislaw Gruszka <sgruszka@redhat.com>,
"Luis R. Rodriguez" <mcgrof@qca.qualcomm.com>,
Jouni Malinen <jouni@qca.qualcomm.com>,
Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>,
Senthil Balasubramanian <senthilb@qca.qualcomm.com>,
Christian Lamparter <chunkeey@googlemail.com>,
Ivo van Doorn <IvDoorn@gmail.com>,
Gertjan van Wingerde <gwingerde@gmail.com>,
Helmut Schaa <helmut.schaa@googlemail.com>,
Larry Finger <Larry.Finger@lwfinger.net>,
Chaoming Li <chaoming_li@realsil.com.cn>,
Arend van Spriel <arend@broadcom.com>,
Luciano Coelho <coelho@ti.com>,
ath9k-devel@venema.h4ckr.net, brcm80211-dev-list@broadcom.com,
users@rt2x00.serialmonkey.com
Subject: Re: [PATCH 5/7] mac80211: Expand powersave configuration flag to be two bits
Date: Wed, 06 Feb 2013 18:44:16 +0100 [thread overview]
Message-ID: <1360172656.7910.60.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20130206170952.GA6280@thinkpad-t410>
On Wed, 2013-02-06 at 11:09 -0600, Seth Forshee wrote:
> > Does it just mean "I support actually turning off the radio"? But then
> > what's the difference to supporting powersave? Can we maybe just
> > disregard wl1251, which has the stupidest powersave implementation on
> > the planet, and solve the "normal" problems first? :)
>
> PS_DOZE means it actually supports putting the hardware into a low-power
> state for powersave. I did take the term from the spec (802.11-2012). It
> is usually used with regard to mesh, but it also appears wrt
> infrastructure BSS (see especially 10.2.1.2 which defines both awake and
> doze in the context of infrastructure networks).
>
> I'm open to other terms, doze just seems to be consistent with the spec.
Thanks for the reference. I had actually thought the term seemed
familiar but then only found mesh references ... need to brush up my
spec knowledge I guess :)
> I haven't considered wl1251 specifically, only enough to update it so
> that it continues to build.
Ah, wl1251 is the weird thing that wants to be told when to wake up/go
to sleep, and then sends nulldata packets itself ... so when we send
nulldata packets *again* for off-channel, because it also uses software
scanning. Like I said before -- "stupidest powersave implementation on
the planet".
> Maybe what's confusing here is that I'm making a differentiation between
> "powersave" as a mac-level feature and "powersave" as a low-power
> hardware state. Which is why I'm trying to change the mac80211
> terminology around so that "doze" now means the low-power state and
> "powersave" refers only to the state in which the AP is bufferring
> frames for us.
Right, ok. Maybe another term would be worthwhile? I mean, *all*
hardware has to support "MAC-level powersave" since you always want
background scanning. The question is how it's implemented ... I'm off
for dinner in a minute but I'll think about it a bit.
> So using these definition powersave is already a mandatory feature for
> any hardware which uses software scanning.
Even offloaded scanning, it's just not visible to mac80211 then.
> All I'm really doing is
> making this explicit, and drivers would now opt in to being placed into
> the doze state rather than opting into powersave in general. And of
> course drivers are now told about transitions to the non-doze powersave
> state (what I'm calling offchannel), so that drivers which need to do
> hardware configuration for this state can do so.
Ok, so maybe just calling it offchannel makes more sense, although that
really interacts only this way with powersave in managed mode, in P2P GO
mode .... oh well.
> > > In practice the changes shouldn't end up much different than what I have
> > > in these patches, but I think it's conceptually cleaner (and less
> > > confusing!). Does this sound reasonable to you?
> >
> > Not really sure I understand it enough to comment :)
>
> I've got working patches now, so maybe those will make everything clear.
> I need to do a little more testing and give them a quick review, then
> I'll send them out.
Ok.
johannes
next prev parent reply other threads:[~2013-02-06 17:43 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 23:47 [PATCH 0/7] Improvements to software scanning Seth Forshee
2013-01-29 23:47 ` [PATCH 1/7] mac80211: Return a status for tx operations Seth Forshee
2013-01-29 23:47 ` [PATCH 2/7] mac80211: Fix tx queue handling during scans Seth Forshee
2013-01-31 15:14 ` Johannes Berg
2013-01-31 16:14 ` Seth Forshee
2013-01-29 23:47 ` [PATCH 3/7] mac80211: Improve error handling for off-channel operation Seth Forshee
2013-01-31 15:15 ` Johannes Berg
2013-01-31 16:17 ` Seth Forshee
2013-01-29 23:47 ` [PATCH 4/7] mac80211: Add flushes before going off-channel Seth Forshee
2013-01-29 23:47 ` [PATCH 5/7] mac80211: Expand powersave configuration flag to be two bits Seth Forshee
2013-01-31 15:20 ` Johannes Berg
2013-01-31 16:33 ` Seth Forshee
2013-01-31 16:53 ` Johannes Berg
2013-01-31 17:18 ` Seth Forshee
2013-01-31 17:50 ` Johannes Berg
2013-02-05 22:51 ` Seth Forshee
2013-02-06 16:48 ` Johannes Berg
2013-02-06 17:09 ` Seth Forshee
2013-02-06 17:44 ` Johannes Berg [this message]
2013-02-06 18:02 ` Seth Forshee
2013-02-06 21:30 ` Johannes Berg
2013-01-29 23:47 ` [PATCH 6/7] mac80211: Add off-channel powersave state Seth Forshee
2013-01-29 23:47 ` [PATCH 7/7] brcmsmac: Add support for off-channel powersave Seth Forshee
2013-01-29 23:56 ` Julian Calaby
2013-01-30 5:28 ` Seth Forshee
2013-01-30 19:34 ` [PATCH 0/7] Improvements to software scanning John W. Linville
2013-01-30 21:27 ` Arend van Spriel
2013-01-30 21:53 ` Seth Forshee
2013-01-31 15:04 ` Johannes Berg
2013-01-31 15:08 ` Johannes Berg
2013-01-31 16:02 ` Seth Forshee
2013-01-31 15:48 ` Seth Forshee
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=1360172656.7910.60.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=IvDoorn@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=arend@broadcom.com \
--cc=ath9k-devel@venema.h4ckr.net \
--cc=brcm80211-dev-list@broadcom.com \
--cc=chaoming_li@realsil.com.cn \
--cc=chunkeey@googlemail.com \
--cc=coelho@ti.com \
--cc=gwingerde@gmail.com \
--cc=helmut.schaa@googlemail.com \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@qca.qualcomm.com \
--cc=senthilb@qca.qualcomm.com \
--cc=seth.forshee@canonical.com \
--cc=sgruszka@redhat.com \
--cc=users@rt2x00.serialmonkey.com \
--cc=vthiagar@qca.qualcomm.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).