From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757509Ab0EGSBK (ORCPT ); Fri, 7 May 2010 14:01:10 -0400 Received: from fifo99.com ([67.223.236.141]:35717 "EHLO fifo99.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756681Ab0EGSBH (ORCPT ); Fri, 7 May 2010 14:01:07 -0400 Subject: Re: [linux-pm] [PATCH 1/8] PM: Add suspend block api. From: Daniel Walker To: Matthew Garrett Cc: Tony Lindgren , Brian Swetland , Alan Stern , mark gross , markgross@thegnar.org, Len Brown , linux-doc@vger.kernel.org, Kernel development list , Jesse Barnes , Oleg Nesterov , Tejun Heo , Linux-pm mailing list , Wu Fengguang , Andrew Morton In-Reply-To: <20100507175159.GB23952@srcf.ucam.org> References: <20100506170151.GA30928@atomide.com> <20100506170956.GA28104@srcf.ucam.org> <20100506171453.GC30928@atomide.com> <1273167311.20494.13.camel@c-dwalke-linux.qualcomm.com> <20100506183605.GF30928@atomide.com> <1273173110.20494.19.camel@c-dwalke-linux.qualcomm.com> <20100507020057.GG30928@atomide.com> <1273252837.3542.30.camel@c-dwalke-linux.qualcomm.com> <20100507173621.GA23604@srcf.ucam.org> <1273254043.3542.37.camel@c-dwalke-linux.qualcomm.com> <20100507175159.GB23952@srcf.ucam.org> Content-Type: text/plain; charset="UTF-8" Date: Fri, 07 May 2010 11:00:55 -0700 Message-ID: <1273255255.3542.43.camel@c-dwalke-linux.qualcomm.com> Mime-Version: 1.0 X-Mailer: Evolution 2.28.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2010-05-07 at 18:51 +0100, Matthew Garrett wrote: > On Fri, May 07, 2010 at 10:40:43AM -0700, Daniel Walker wrote: > > On Fri, 2010-05-07 at 18:36 +0100, Matthew Garrett wrote: > > > If your wakeup latencies are sufficiently low and you have fine-grained > > > enough control over your hardware then suspend in idle is a reasonable > > > thing to do - but if you have a userspace app that's spinning then > > > that doesn't solve the issue. > > > > If there's a userspace app spinning then you don't go idle (or that's my > > assumption anyway). You mean like repeatedly blocking and unblocking > > right? > > Right, that's the problem. idle-based suspend works fine if your > applications let the system go idle, but if your applications are > anything other than absolutely perfect in this respect then you consume > significant power even if the device is sitting unused in someone's > pocket. True .. I'd wonder how an OMAP based devices deal with that issue, since they would have that exact problem. According to what Tony is telling us. Actually a bogus userspace can do a lot more than just consume power you could hang the system too. Daniel