From: Seth Forshee <seth.forshee@canonical.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org,
"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: Thu, 7 Feb 2013 14:10:44 -0600 [thread overview]
Message-ID: <20130207201044.GC4378@thinkpad-t410> (raw)
In-Reply-To: <51140811.3000108@broadcom.com>
On Thu, Feb 07, 2013 at 09:01:21PM +0100, Arend van Spriel wrote:
> On 02/07/2013 07:15 PM, Seth Forshee wrote:
> > On Wed, Feb 06, 2013 at 10:32:02PM +0100, Johannes Berg wrote:
> >> 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
> >
> > Hmm, I guess I should have mentioned that these patches were written on
> > top of the version 2 patches I sent for adding the off-channel queue
> > stop reason, etc. I'll need to resend them before they're likely to
> > apply cleanly anywhere.
> >
> >> That's a lot of driver changes ... :)
> >
> > A large number of those changes were made by sed ;-)
> >
> >> 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
> >
> > I tried to ensure that the patches would result in equivalent behavior
> > for all drivers except brcmsmac (which will behave better). But I
> > obviously wan't able to test every driver to verify this.
> >
> > I suspect b43 should also be updated similarly to brcmsmac. The only
> > hardware I have that uses b43 is a macbook whose wireless functions too
> > poorly to be a good test case.
>
> If I recall correctly b43 has a Kconfig option to allow it to support
> the same devices brcmsmac supports.
You're right; I forgot about that. It looks like that will make it at
least claim to support my BCM43224. I'll have to give that a try.
Thanks for the suggestion.
Seth
prev parent reply other threads:[~2013-02-07 20:10 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 ` [PATCH 0/4] Add support for off-channel powersave state in mac80211 Johannes Berg
2013-02-07 18:15 ` Seth Forshee
2013-02-07 20:01 ` Arend van Spriel
2013-02-07 20:10 ` Seth Forshee [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=20130207201044.GC4378@thinkpad-t410 \
--to=seth.forshee@canonical.com \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).