Hi,
This is an open discussion about android wakelock. Currently we have a
kernel support of them.
In the power directory we have:
/power/wake_lock
/power/wake_full_lock --> I add this one for a backword compatibility,
but I will removed soon
/power/wake_unlock
/power/state
Each wake lock has associated a timeout and a name. When the timeout is
not defined the lock
is taken until an unlock call.
These are used by the hardware layer and ril library (one part of the
ril is currently closed)
The wake_lock are used to avoid kernel suspend when one of theme is
acquired.
Ok the system is a mapped software layer on the wake lock
PARTIAL_WAKE_LOCK
FULL_WAKE_LOCK
...
and other one.
These are used in resuming part when the system must decide if:
- resume the cpu only PARTIAL WAKE LOCK (keyboard)
- reusme the cpu and full light display FULL_WAKE_LOCK (ril subsystem)
- and other that are not used
Well the keyboard acquire (I think look at the code) a PARTIAL WAKE
LOCK, so the display remains black and
for a correct power one you must click the power button two times. The
idea is to investigate and check
if the freerunner fit in these schemes or propose somenthing different,
because we don't have keyboard or
light on that.
Michael
_______________________________________________
android-freerunner mailing list
[email protected]
http://android.koolu.org/listinfo.cgi/android-freerunner-koolu.org
