Hi!
too heavy (in fact it's much lighter weight than resuming all devices
that your approach doesn't prevent from happening, so for example on my
desktop/notebook machines I woulnd't mind at all if user space were
thawed after all of the devices had been resumed).
Well, it would
On Tuesday, April 26, 2011, Pavel Machek wrote:
Hi!
too heavy (in fact it's much lighter weight than resuming all devices
that your approach doesn't prevent from happening, so for example on my
desktop/notebook machines I woulnd't mind at all if user space were
thawed after all
Hi!
And that's exactly what should be done. Have a user space process
controlling
that, because avoiding to thaw user space doesn't buy us almost
anything.
That makes Zaurus implement different user-kernel interface than PC
class machine, because of hardware quirk.
Let me
On Tuesday, April 26, 2011, Rafael J. Wysocki wrote:
On Tuesday, April 26, 2011, Pavel Machek wrote:
...
Ok, see the spitz_should_wakeup() function in arch/arm/mach-pxa/* and
should_wakeup() usage.
OK, I will.
Well, as far as I can tell, on Zaurus this is all done within the platform
