On Monday, 2. February 2009, Pavel Machek wrote: > On Sun 2009-02-01 00:20:04, Rafael J. Wysocki wrote: > > On Saturday 31 January 2009, Arve Hj?nnev?g wrote: > > > On Sat, Jan 31, 2009 at 7:41 AM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > > > > On Fri, 30 Jan 2009, Brian Swetland wrote: > > > >> Imagine the computer in question is a cellphone which is going to > > > >> need to wake up when a call comes in to do traditional cellphone > > > >> things, like ring, bring up the incall UI (so the user can > > > >> answer/cancel), etc. > > > > > > > > Yes. So what? Nothing I said prevents the computer from waking up > > > > when a call comes in. What I said was that when the user tells the > > > > computer to suspend (e.g., by writing "mem" to /sys/power/state), the > > > > computer should suspend even if some wakelocks are still locked. > > > > > > But this could prevent the phone from ringing. What if the user-space > > > code that is responsible for playing the ringtone has been notified > > > that a call is coming in and starts reading the audio file with the > > > ringtone. At the same, the user, unaware that someone is calling, > > > presses the power button. If we ignore the wakelock in this situation, > > > the phone will not ring. > > Yes, you don't want to write "mem" to /sys/power/state on android. You > want to write something like "auto-mem" there. > ACK. Don't change the way "mem" works. Just don't use it if it does the wrong thing on android. Uli -- ------- ROAD ...the handyPC Company - - - ) ) ) Uli Luckas Head of Software Development ROAD GmbH Bennigsenstr. 14 | 12159 Berlin | Germany fon: +49 (30) 230069 - 62 | fax: +49 (30) 230069 - 69 url: www.road.de Amtsgericht Charlottenburg: HRB 96688 B Managing director: Hans-Peter Constien _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
