From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: [RFC] sleepy linux Date: Wed, 26 Dec 2007 21:17:22 +0100 Message-ID: <20071226201722.GC8844@elf.ucw.cz> References: <20071225230731.GA29030@elf.ucw.cz> <200712261828.04671.oliver@neukum.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <200712261828.04671.oliver@neukum.org> 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: Oliver Neukum Cc: Linux-pm mailing list , kernel list List-Id: linux-pm@vger.kernel.org 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 > > =A0 > > This is RFC. It does not even work for me... it sleeps but it will no= t > > wake up, because SATA wakeup code is missing. Code attached for illus= tration. > >=20 > > I wonder if this is the right approach? What is right interface to th= e > > drivers? >=20 > 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? I guess I need to know from atomic context :-(. Pavel --=20 (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/b= log.html From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752497AbXLZURp (ORCPT ); Wed, 26 Dec 2007 15:17:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751528AbXLZURh (ORCPT ); Wed, 26 Dec 2007 15:17:37 -0500 Received: from gprs189-60.eurotel.cz ([160.218.189.60]:37784 "EHLO amd.ucw.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751514AbXLZURg (ORCPT ); Wed, 26 Dec 2007 15:17:36 -0500 Date: Wed, 26 Dec 2007 21:17:22 +0100 From: Pavel Machek To: Oliver Neukum Cc: kernel list , Linux-pm mailing list , "Rafael J. Wysocki" Subject: Re: [RFC] sleepy linux Message-ID: <20071226201722.GC8844@elf.ucw.cz> References: <20071225230731.GA29030@elf.ucw.cz> <200712261828.04671.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: <200712261828.04671.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 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? I guess I need to know from atomic context :-(. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html