http://bugzilla.kernel.org/show_bug.cgi?id=6892
------- Comment #31 from [EMAIL PROTECTED] 2008-08-18 01:30 -------
My vote is still what I suggested in comment #2: just call resume(). Nobody
has come up with a reason why that would be inappropriate ...
Re: "I assume no device can enter suspend mode in runtime" ... bad
assumption!!! Even just on PCs, but especially with embedded Linux hardware.
I already gave the example of USB, where a number of drivers support it today
even on PCs. The "autosuspend" mechanisms handle that, and root hubs (in
particular) did it for a long time before that infrastructure existed.
Linux drivers for embedded hardware fairly routinely adopt strategies where
they enter low power modes ("suspend") whenever they don't actually need to be
active. You wouldn't get over a week of battery life from a Nokia N810 tablet
without aggressive runtime PM ... those little cell phone batteries can't store
much power.
(And there's upcoming OMAP3 stuff that's very interesting ... not yet merged to
mainline. When the last clock in a power domain is disabled, and drivers
support it, those power domains can be automatically switched off to eliminate
leakage current. As you probably know, that's become more important with
recent generations of process technology.)
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
