From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: [RFC][PATCH 00/11] Android PM extensions Date: Wed, 4 Feb 2009 14:25:13 +0100 Message-ID: <20090204132513.GA1218@ucw.cz> References: <1233611258.21871.101.camel@nigel-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: Arve Hj?nnev?g Cc: Brian Swetland , Nigel Cunningham , Uli Luckas , linux-pm@lists.linux-foundation.org List-Id: linux-pm@vger.kernel.org Hi! > wrote: > > It sounds to me like all of this stuff is just power management of > > individual devices, which should be done through the sysfs interface and > > completely unrelated to /sys/power/state. > > It is easier for us to add a hook to the individual drivers than to > maintain a list of devices in user-space. Also, last time I checked, > the only way to disable individual devices was through a deprecated > interface. Is there a new way to do this? No, but we need one, sooner or later. I'd say that implementing nice device power management would be better than early-suspend hack. > > That said, if suspend to ram is what they really want for 'auto-mem', > > what you're suggesting sounds good to me. > > Suspend gives us two advantages over idle. All threads are frozen > which means that an app that is using too much cpu time no longer > drains the battery. And, the monotonic clock stops. SIGSTOP should be the right tool if some application uses too much cycles... -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html