From: Kalle Valo <kalle.valo@nokia.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org, "Felix Fietkau" <nbd@openwrt.org>
Subject: Re: Thoughts about mac80211 client PS implementation
Date: Wed, 05 Nov 2008 23:06:11 +0200 [thread overview]
Message-ID: <87bpwtkhmk.fsf@nokia.com> (raw)
In-Reply-To: <43e72e890811051243y65f8b51cy2f80279ecbebc8e4@mail.gmail.com> (ext Luis R. Rodriguez's message of "Wed\, 5 Nov 2008 12\:43\:06 -0800")
Luis R. Rodriguez <mcgrof@gmail.com> writes:
> On Wed, Nov 5, 2008 at 12:33 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
>> On Wed, 2008-11-05 at 22:27 +0200, Kalle Valo wrote:
>
> BTW who defines "Dynamic Power Save"?
No idea, we have been just using that name internally.
> Is there a standard approach or more an implementation approach to
> the concept of doing PS while active?
AFAIK the standard only talks about the part which I call "static PS",
that is PS-Polling frames from the AP. It doesn't mention anything
about when enabling and disabling it, unfortunately.
>>> PS should be disabled while associated and running software scan, and
>>> naturally re-enabled after the scan has finished. I assume hardware
>>> scanning implementations are clever enough to disable PS when scanning
>>> and we don't have to worry about that case.
>
> BTW we need to check if in ath5k/ath9k if the beacon miss interrupt
> will actually be triggered *if* the beacon filter is *off*. Not sure
> about this yet. Also I'm not sure if triggering scanning will enable
> beaconing filter in our hardware if its off and then disable it after
> scanning too.
Actually beacon filtering is a different subject from 802.11 Power
Save. Beacon filtering improves the host's (CPU) power consumption (by
reducing it's wakeups) and 802.11 PS improves the power consumption of
the wireless chip (by reducing the time transceiver is enabled). In
other words, we can enable Power Save but still the host can receive
all the beacons.
Beacon filtering is next on my agenda as soon as I can finish the
Power Save part.
--
Kalle Valo
next prev parent reply other threads:[~2008-11-05 21:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 20:27 Thoughts about mac80211 client PS implementation Kalle Valo
2008-11-05 20:33 ` Johannes Berg
2008-11-05 20:43 ` Luis R. Rodriguez
2008-11-05 21:06 ` Kalle Valo [this message]
2008-11-06 12:20 ` Felix Fietkau
2008-11-05 20:54 ` Kalle Valo
2008-11-05 21:05 ` Johannes Berg
2008-11-05 21:25 ` Kalle Valo
2008-11-05 21:55 ` Tomas Winkler
2008-11-06 7:35 ` Kalle Valo
2008-11-06 11:00 ` Johannes Berg
2008-11-07 16:06 ` Johannes Berg
2008-11-07 17:58 ` Kalle Valo
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=87bpwtkhmk.fsf@nokia.com \
--to=kalle.valo@nokia.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=nbd@openwrt.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;
as well as URLs for NNTP newsgroup(s).