From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 8) Date: Thu, 27 May 2010 19:23:03 +0100 Message-ID: <20100527182303.GM3543@srcf.ucam.org> References: <20100527140655.GA28048@srcf.ucam.org> <20100527155201.GA31937@srcf.ucam.org> <20100527165931.GB1062@srcf.ucam.org> <20100527172343.GB2468@srcf.ucam.org> <20100527184918.3d090921@lxorguk.ukuu.org.uk> <20100527175030.GA3543@srcf.ucam.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Thomas Gleixner Cc: Alan Cox , Arve =?iso-8859-1?B?SGr4bm5lduVn?= , Florian Mickler , Vitaly Wool , Peter Zijlstra , LKML , Paul@smtp1.linux-foundation.org, felipe.balbi@nokia.com, Linux OMAP Mailing List , Linux PM List-Id: linux-omap@vger.kernel.org On Thu, May 27, 2010 at 08:18:49PM +0200, Thomas Gleixner wrote: > On Thu, 27 May 2010, Matthew Garrett wrote: > > Actually, the reverse - there's no terribly good way to make PCs work > > with scheduler-based suspend, but there's no reason why they wouldn't > > work with the current opportunistic suspend implementation. > > How does that solve the problems you mentioned above ? Wakeup > guarantees, latencies ... Latency doesn't matter because we don't care when the next timer is due to expire. Wakeup guarantees can be provided via the suspend blocker implementation. -- Matthew Garrett | mjg59@srcf.ucam.org