From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [RFC] sleepy linux Date: Sun, 30 Dec 2007 12:15:52 +0100 Message-ID: <20071230111552.GA8578@elte.hu> References: <20071225230731.GA29030@elf.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20071225230731.GA29030@elf.ucw.cz> Sender: linux-kernel-owner@vger.kernel.org To: Pavel Machek Cc: kernel list , Linux-pm mailing list , "Rafael J. Wysocki" List-Id: linux-pm@vger.kernel.org * Pavel Machek wrote: > Todays hardware is mostly capable of doing better: with correctly set > up wakeups, machine can sleep and successfully pretend it is not > sleeping -- by waking up whenever something interesting happens. Of > course, it is easier on machines not connected to the network, and on > notebook computers. > > Requirements: > > 0) Working suspend-to-RAM, with kernel being able to bring video back. > > 1) RTC clock that can wake up system very nice approach! It might require smarter hardware to be really efficient, but the generic ability for Linux to utilize S3 automatically would _quickly_ drive the creation of smarter hardware i'm sure - so i'd propose to include this even if it wastes power in some cases. a quick feature request: could you please make the wake-on-RTC capability generic and add a CONFIG_DEBUG_SUSPEND_ON_RAM=y config option (disabled by default) that does a short 1-second suspend-to-RAM sequence upon bootup? That way we could test s2ram automatically (which is a MUCH needed feature for automated regression testing and automatic bisection). In addition, some sort of 'suspend for N seconds' /sys or /dev/rtc capability would be nice as well. btw., how far are you from having a working prototype? Ingo