From: Johannes Berg <johannes@sipsolutions.net>
To: Krishna Chaitanya <chaitanya.mgit@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH V3] mac80211: wowlan: suspend: Fix power save state stuck in ACTIVE caused by race between suspend and Tx packet.
Date: Wed, 17 Jun 2015 13:01:49 +0200 [thread overview]
Message-ID: <1434538909.1884.39.camel@sipsolutions.net> (raw)
In-Reply-To: <CABPxzYL0rnht72K1fLcpyjC=eOM4nHxzHQRpD47iE6J=J-3sOg@mail.gmail.com> (sfid-20150617_122259_357472_BB8516CF)
On Wed, 2015-06-17 at 15:52 +0530, Krishna Chaitanya wrote:
> > I still don't like it. I also don't believe that what you're writing is
> > actually true. The only problem I can see is that it leads to higher
> > power consumption *while the system is suspended* - at resume time we
> > send a packet and thus kick the timers...
> "If" we send a packet, but until them the system will still be
> active.
But we *always* send a packet:
ieee80211_reconfig:
...
/*
* The sta might be in psm against the ap (e.g. because
* this was the state before a hw restart), so we
* explicitly send a null packet in order to make sure
* it'll sync against the ap (and get out of psm).
*/
if (!(local->hw.conf.flags & IEEE80211_CONF_PS)) {
list_for_each_entry(sdata, &local->interfaces, list) {
if (sdata->vif.type != NL80211_IFTYPE_STATION)
continue;
if (!sdata->u.mgd.associated)
continue;
ieee80211_send_nullfunc(local, sdata, 0);
}
}
Then again, you're talking about WoWLAN, but then ...
johannes
next prev parent reply other threads:[~2015-06-17 11:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 13:42 [PATCH V3] mac80211: wowlan: suspend: Fix power save state stuck in ACTIVE caused by race between suspend and Tx packet Chaitanya T K
2015-06-17 8:47 ` Johannes Berg
2015-06-17 10:22 ` Krishna Chaitanya
2015-06-17 11:01 ` Johannes Berg [this message]
2015-06-17 11:35 ` Krishna Chaitanya
2015-06-17 11:37 ` Johannes Berg
2015-06-17 12:15 ` Krishna Chaitanya
2015-07-17 9:16 ` Johannes Berg
2015-07-17 9:33 ` Krishna Chaitanya
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=1434538909.1884.39.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=chaitanya.mgit@gmail.com \
--cc=linux-wireless@vger.kernel.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).