From: Johannes Berg <johannes@sipsolutions.net>
To: Seth Forshee <seth.forshee@canonical.com>
Cc: linux-wireless@vger.kernel.org,
Arend van Spriel <arend@broadcom.com>,
"John W. Linville" <linville@tuxdriver.com>,
brcm80211-dev-list@broadcom.com
Subject: Re: [PATCH 0/4] Add support for off-channel powersave state in mac80211
Date: Wed, 06 Feb 2013 22:32:02 +0100 [thread overview]
Message-ID: <1360186322.7910.76.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1360184478-31481-1-git-send-email-seth.forshee@canonical.com>
On Wed, 2013-02-06 at 15:01 -0600, Seth Forshee wrote:
> Hi Johannes,
>
> As promised, here are the patches which add the off-channel powesave
> state. At a high level, the changes are:
>
> * Expand the PS configuration flag to be 2 bits and add helper
> functions for reading and setting the modes
> * Change the terminology around PS states, i.e. disabled -> awake and
> enabled -> doze
> * Add the off-channel PS state and put it to use
> * Minor driver updates based on these changes
> * Update brcmsmac to utilize the off-channel PS state
That's a lot of driver changes ... :)
I've been trying to disentangle the mess a bit. It looks like I was
completely wrong about wl1251, it has HW scan so we don't care about its
weird PS behaviour (1).
That leaves us with a few different drivers:
* iwlegacy -- has PS support but not NULLFUNC_STACK, so generates a
wakeup to the AP when we want to go scan ...
* drivers like iwlwifi/wl12xx have HW scan and don't set NULLFUNC_STACK
* drivers like ath5k/9k/... have all SW but set NULLFUNC_STACK
* drivers that just don't have powersave
So I guess iwlegacy is kinda the weird case and not wl1251 ... Oh well.
So for those that have HW scan we just don't have to worry about all of
this, since they never run the scan code :-)
Ok now I forgot where I was going with this ... oops. I'll look at the
code and patches some more.
johannes
(1) let's leave aside remain-on-channel for now, I think we should
probably go and require that drivers set a "I support this" flag, since
it is otherwise almost certain to not work ... it also only matters for
P2P and 11u, so no big deal for old drivers
next prev parent reply other threads:[~2013-02-06 21:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 21:01 [PATCH 0/4] Add support for off-channel powersave state in mac80211 Seth Forshee
2013-02-06 21:01 ` [PATCH 1/4] mac80211: Convert PS configuration from a binary flag to a set of modes Seth Forshee
2013-02-13 15:06 ` Johannes Berg
2013-02-13 17:04 ` Seth Forshee
2013-02-13 18:54 ` Arend van Spriel
2013-02-13 19:09 ` Johannes Berg
2013-02-13 19:25 ` Seth Forshee
2013-02-13 21:36 ` Seth Forshee
2013-02-13 21:43 ` Arend van Spriel
2013-02-13 22:00 ` Seth Forshee
2013-02-15 12:20 ` Johannes Berg
2013-02-06 21:01 ` [PATCH 3/4] mac80211: Add off-channel PS state Seth Forshee
2013-02-06 21:01 ` [PATCH 4/4] brcmsmac: Add support for off-channel powersave Seth Forshee
2013-02-06 21:32 ` Johannes Berg [this message]
2013-02-07 18:15 ` [PATCH 0/4] Add support for off-channel powersave state in mac80211 Seth Forshee
2013-02-07 20:01 ` Arend van Spriel
2013-02-07 20:10 ` 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=1360186322.7910.76.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=seth.forshee@canonical.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).