Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752620AbXLZUdX (ORCPT ); Wed, 26 Dec 2007 15:33:23 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751585AbXLZUdO (ORCPT ); Wed, 26 Dec 2007 15:33:14 -0500 Received: from gprs189-60.eurotel.cz ([160.218.189.60]:47499 "EHLO amd.ucw.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751377AbXLZUdN (ORCPT ); Wed, 26 Dec 2007 15:33:13 -0500 Date: Wed, 26 Dec 2007 21:32:58 +0100 From: Pavel Machek To: Oliver Neukum Cc: kernel list , Linux-pm mailing list , "Rafael J. Wysocki" Subject: Re: [RFC] sleepy linux Message-ID: <20071226203258.GE8094@elf.ucw.cz> References: <20071225230731.GA29030@elf.ucw.cz> <200712261828.04671.oliver@neukum.org> <20071226201722.GC8844@elf.ucw.cz> <200712262123.37152.oliver@neukum.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200712262123.37152.oliver@neukum.org> X-Warning: Reading this can be dangerous to your mental health. User-Agent: Mutt/1.5.16 (2007-06-11) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2024 Lines: 50 On Wed 2007-12-26 21:23:37, Oliver Neukum wrote: > Am Mittwoch, 26. Dezember 2007 21:17:22 schrieb Pavel Machek: > > On Wed 2007-12-26 18:28:04, Oliver Neukum wrote: > > > Am Mittwoch, 26. Dezember 2007 00:07:31 schrieb Pavel Machek: > > > > Heute 00:07:31 > > > > ? > > > > This is RFC. It does not even work for me... it sleeps but it will not > > > > wake up, because SATA wakeup code is missing. Code attached for illustration. > > > > > > > > I wonder if this is the right approach? What is right interface to the > > > > drivers? > > > > > > IMHO you are making to many special cases. The system can be "sleepy" > > > if all devices can be runtime suspended and all CPUs are idle. > > > > Is there an easy way to tell if all the devices are runtime suspended? > > Do you really want to know whether they are suspended or whether they > could be suspended? If they are suspended. My plan is: let the drivers autosuspend on their own. If I see all of them are autosuspended, then it looks like great time to put whole system into s2ram... > > I guess I need to know from atomic context :-(. > > Urgh. suspend() must be able to sleep and can fail. That's ok. ... I also don't need to call any suspend() routines, because all the drivers are already suspended, right? And yes, I want device activity to prevent s2ram. If user is burning CD, machine should not sleep. If user is actively typing, machine should not sleep. My vision is: screen saver tells kernel keyboard need not be very responsive, at that point keyboard driver can autosuspend the keyboard, and if that was the last device, whole system sleeps. 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/