On Thu, May 27, 2010 at 1:17 AM, Bernd Petrovitsch <bernd@xxxxxxxxxxxxxxxxxxx> wrote: > On Mit, 2010-05-26 at 13:23 -0500, James Bottomley wrote: >> On Wed, 2010-05-26 at 19:51 +0200, Thomas Gleixner wrote: > [...] >> > Darn, _we_ have to deal with that forever as it sets a crappy user >> > space ABI in stone. >> >> I really don't see how it is ... the ABI comes with a switch that allows >> it to be disabled, so only platforms wishing to use it have to support >> it. Even on those platforms that do support it, we can translate most > > You completely missed the point: The crappy user interface - and > interferences with pother subsystems - must be maintained for ages - and > that is independent if one uses it or not. Even worse if it's not widely > used. When (or if) the time comes that suspend is no longer useful, this api becomes a NOP. > >> of it into pm QoS stuff and if one day someone solves the rogue app >> problem, we can migrate over. > > If it's so important for Android and no one else, Android can carry it > out of tree. > This is not only important for Android. If you use suspend on a current Linux system you run the risk of loosing wakeup events. If you have wakeup events that you cannot afford to lose your only option is to never suspend. On some hardware (e.g. x86) the cost of not suspending is always huge, on other hardware (many ARM SOCs) the cost is only huge if your apps behave poorly. -- Arve Hjønnevåg _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
