[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110426211159.GB28033@elf.ucw.cz>
Date: Tue, 26 Apr 2011 23:11:59 +0200
From: Pavel Machek <pavel@....cz>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Greg KH <gregkh@...e.de>, MyungJoo Ham <myungjoo.ham@...sung.com>,
linux-pm@...ts.linux-foundation.org,
Len Brown <len.brown@...el.com>,
"Jean Delvare (PC drivers core)" <khali@...ux-fr.org>,
"Ben Dooks (embedded platforms)" <ben-linux@...ff.org>,
kyungmin.park@...sung.com, myungjoo.ham@...il.com,
LKML <linux-kernel@...r.kernel.org>,
Alan Stern <stern@...land.harvard.edu>
Subject: Re: [RFC PATCH v2 1/3] PM / Core: suspend_again callback for
device PM.
Hi!
> > > What is the root problem that this is trying to solve?
> >
> > It is trying to fix machines that need to run periodic kernel tasks
> > even when user asked them to sleep. Zaurus needs to periodicaly wake
> > up to be able to charge battery in s2ram state, for example.
>
> Well, if you wake up periodically, it's not S2RAM any more, I'd say.
It certainly looks a lot like s2ram to the user.
Now, your PC wakes up periodically in s2ram, too; but it is keyboard
controller that wakes up, not CPU, so you do not know.
On Zaurus, you do not know, either; nothing visible happens and
userspace is shielded from these details.
Should user really have to know if battery charger is implemented on
keyboard controller or on main cpu before he selects which interface
to use?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists