Re: [linux-pm] [PATCH] Custom power states for non-ACPI systems

[Pavel Machek <pavel@ucw.cz>]

Hi!

> > These are expected to be system states, and sleeping system
> > does not take calls, etc...
> 
> Pavel, remember that great big "wakeup" shaped hole in the
> current PM framework... ?  Even ACPI sleep states support
> wakeup mechanisms, although not well under Linux (yet).

Umm, yes, I see that one.

> One way a sleeping system could take a call is if some
> external chip raised a wakeup-enabled IRQ to wake up the
> system.  And if going from deep sleep to normal operational
> state has a low cost, why shouldn't the system routinely
> enter deep sleep instead of going to CPU idle state?

But in such case /sys/power/sleep is wrong interface to trigger
this. Imagine system taking short sleeps 10 times a second. You don't
want to trigger that using /sys/power/sleep [because it would switch
your consoles].

But yes, I see the fine line... If it turns display off and waits for
incoming call, yes, there /sys/power/sleep makes sense. Someone get me
Linux phone or tell me where to buy one so I can see the fine points
better ;-).
								Pavel
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!