From: Johannes Berg <johannes@sipsolutions.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH 5/7] mac80211: Expand powersave configuration flag to be two bits
Date: Wed, 06 Feb 2013 22:30:06 +0100 [thread overview]
Message-ID: <1360186206.7910.75.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <20130206180227.GB6280@thinkpad-t410>
On Wed, 2013-02-06 at 12:02 -0600, Seth Forshee wrote:
> > 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".
>
> Ah, I had wondered what hardware that code was there for :-)
I was actually wrong -- wl1251 has HW scan so it doesn't matter.
However, iwlegacy does this...
> So I think the approach I'm advocating could possibly make things better
> for wl1251. If it's told about going to off-channel powersave rather
> than being told it's leaving powersave, maybe it can do the right thing
> with the nullfunc frames without mac80211 generating the extra nullfunc.
> I don't know that for sure though because I don't understand how the
> hardware works.
Probably not. For iwlegacy anyway it won't help.
> > > 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.
>
> Okay, sure. I'm just thinking of things from the mac80211 perspective.
Right, sure.
> > > 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.
>
> I admit I've only been considering managed mode and know next to nothing
> about P2P GO mode. If I'm creating problems for any other modes I'd
> definitely like to know about it so I can take it into consideration.
No no, I'm just saying there "powersave" could have even more
meanings ...
johannes
prev parent reply other threads:[~2013-02-06 21:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1359503255-18270-1-git-send-email-seth.forshee@canonical.com>
2013-01-29 23:47 ` [ath9k-devel] [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
2013-02-06 18:02 ` Seth Forshee
2013-02-06 21:30 ` Johannes Berg [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=1360186206.7910.75.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath9k-devel@lists.ath9k.org \
/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