Update on Android PM enhancements - CONFIG_HAS_EARLYSUSPEND and friends

Arve,

What ever happened with your series on the Android PM extensions you
had submitted in 2009 [1] ? I'm working on ath6kl right now and I'm
going to remove all that early suspend crap as its not upstream and I
want to get ath6kl into upstream proper. Do you have plans for a
replacement? Since the thread covers wake locks, have you ironed out
what you are going to do with that as well?

[1] https://lists.linux-foundation.org/pipermail/linux-pm/2009-February/019498.html

  Luis

On Wed, Mar 23, 2011 at 01:05:47PM -0700, Luis R. Rodriguez wrote:

Arve,

What ever happened with your series on the Android PM extensions you
had submitted in 2009 [1] ? I'm working on ath6kl right now and I'm
going to remove all that early suspend crap as its not upstream and I
want to get ath6kl into upstream proper. Do you have plans for a
replacement? Since the thread covers wake locks, have you ironed out
what you are going to do with that as well?

Wake locks are all taken care of, see:
	http://lwn.net/Articles/416690/
for the details.

thanks,

greg k-h

2011/3/23 Luis R. Rodriguez [off-list ref]:

Arve,

What ever happened with your series on the Android PM extensions you
had submitted in 2009 [1] ? I'm working on ath6kl right now and I'm
going to remove all that early suspend crap as its not upstream and I
want to get ath6kl into upstream proper. Do you have plans for a
replacement?

There is no planned replacement for early suspend, and it will
probably be dropped form the android kernel at some point. The wifi
driver use it to enter a lower operating state when the screen is off.
If you driver does have any other way to put the driver in this state
you need to add an interface that lets user-space select that state
directly.

Since the thread covers wake locks, have you ironed out
what you are going to do with that as well?

The wakelock code did not get merged. Instead there is a new interface
that should provide the same functionality to drivers, but this has
not integrated with android yet (and you cannot use it directly as it
does not provide the same user-space interface). In theory, you should
be able to replace all the wakelocks in your driver with calls to the
mainline api. Even if you cannot test the result this is better than
just deleting the wakelocks.

-- 
Arve Hjønnevåg

On Wed, 2011-03-23 at 17:47 -0700, Arve Hjønnevåg wrote:

There is no planned replacement for early suspend, and it will
probably be dropped form the android kernel at some point. The wifi
driver use it to enter a lower operating state when the screen is off.
If you driver does have any other way to put the driver in this state
you need to add an interface that lets user-space select that state
directly.

The interface is called "ip link set wlan0 down".

johannes

On Thu, 2011-03-24 at 10:04 +0100, Johannes Berg wrote:

On Wed, 2011-03-23 at 17:47 -0700, Arve Hjønnevåg wrote:

quoted

There is no planned replacement for early suspend, and it will
probably be dropped form the android kernel at some point. The wifi
driver use it to enter a lower operating state when the screen is off.
If you driver does have any other way to put the driver in this state
you need to add an interface that lets user-space select that state
directly.

The interface is called "ip link set wlan0 down".

Or, in fact, just powersaving mode. But I don't think for a wifi driver
there's any need for special driver specific states.

johannes