From: Kalle Valo <kvalo@adurom.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Arve Hjønnevåg" <arve@android.com>,
"Luis R. Rodriguez" <mcgrof@gmail.com>,
linux-kernel@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>,
devel@linuxdriverproject.org, "Naveen Singh" <nsingh@atheros.com>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Jouni Malinen" <Jouni.Malinen@atheros.com>,
"Vipin Mehta" <vmehta@atheros.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Update on Android PM enhancements - CONFIG_HAS_EARLYSUSPEND and friends
Date: Wed, 30 Mar 2011 09:03:54 +0300 [thread overview]
Message-ID: <87vcz1rvp1.fsf@purkki.adurom.net> (raw)
In-Reply-To: <87k4fouamf.fsf@purkki.adurom.net> (Kalle Valo's message of "Thu\, 24 Mar 2011 11\:32\:40 +0200")
Kalle Valo <kvalo@adurom.com> writes:
> In maemo, to save power, we decreased the dynamic power save timeout
> whenever display was turned off. This was all done from user space and
> wifi driver in the kernel was completely unaware of the display state.
[...]
> And before someone suggests adding dynamic timeout variable to
> nl80211: I think it's very much implementation specific parameter. Not
> all drivers support it and it might be that even in future mac80211
> uses something else. So having the timeout variable in nl80211 is not
> a long term solution.
I totally forgot that Juuso added QoS requirements support to
mac80211. And that's the proper wayq to do this, user space sets QoS
requirements based on display state, and whatever else it thinks is
important, and mac80211 adapts the power save parameters accordingly.
In this method we are not revealing any implemention details to user
space, and that's always a good thing.
--
Kalle Valo
prev parent reply other threads:[~2011-03-30 6:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 20:05 Luis R. Rodriguez
2011-03-23 20:28 ` Greg KH
2011-03-24 0:47 ` Arve Hjønnevåg
2011-03-24 9:04 ` Johannes Berg
2011-03-24 9:06 ` Johannes Berg
2011-03-24 9:32 ` Kalle Valo
2011-03-30 6:03 ` Kalle Valo [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=87vcz1rvp1.fsf@purkki.adurom.net \
--to=kvalo@adurom.com \
--cc=Jouni.Malinen@atheros.com \
--cc=arve@android.com \
--cc=benh@kernel.crashing.org \
--cc=devel@linuxdriverproject.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=nsingh@atheros.com \
--cc=rjw@sisk.pl \
--cc=vmehta@atheros.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
all inboxes | Powered by JetHome®