Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755609Ab0FFKuH (ORCPT ); Sun, 6 Jun 2010 06:50:07 -0400 Received: from ist.d-labs.de ([213.239.218.44]:49866 "EHLO mx01.d-labs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754783Ab0FFKuF (ORCPT ); Sun, 6 Jun 2010 06:50:05 -0400 Date: Sun, 6 Jun 2010 12:49:49 +0200 From: Florian Mickler To: Vitaly Wool Cc: david@lang.hm, Brian Swetland , Arve =?ISO-8859-15?Q?Hj=F8nnev=E5g?= , Arjan van de Ven , tytso@mit.edu, Peter Zijlstra , "H. Peter Anvin" , LKML , Neil Brown , James Bottomley , Alan Cox , Linux PM , Ingo Molnar , Linux OMAP Mailing List , Linus Torvalds , Thomas Gleixner , Felipe Balbi Subject: Re: [linux-pm] suspend blockers & Android integration Message-ID: <20100606124949.539fa636@schatten.dmk.lab> In-Reply-To: References: <20100603193045.GA7188@elte.hu> <20100604071354.GA14451@elte.hu> <20100604083423.GD15181@elte.hu> <1275653210.27810.39762.camel@twins> <1275731653.27810.41078.camel@twins> <20100605092851.6ee15f13@infradead.org> X-Mailer: Claws Mail 3.7.5 (GTK+ 2.18.9; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1409 Lines: 38 On Sun, 6 Jun 2010 12:19:08 +0200 Vitaly Wool wrote: > 2010/6/6 : > > > as an example (taken from this thread). > > > > system A needs to wake up to get a battery reading, store it and go back to > > sleep, It does so every 10 seconds. But when it does so it only runs the one > > process and then goes back to sleep. > > > > system B has the same need, but wakes up every 10 minutes. but when it does > > so it fully wakes up and this allows the mail app to power up the radio, > > connect to the Internet and start checking for new mail before oppurtunistic > > sleep shuts things down (causing the mail check to fail) > > > > System A will last considerably longer on a battery than System B. > > Exactly, thanks for pointing out the specific example :) > > ~Vitaly This does not affect suspend_blockers nor does suspend_blockers interfere with that. Suspend_blockers allow the system to suspend ("mem">/sys/power/state suspend), when the userspace decides that the device is not in use. So implementing suspend_blockers support does not impact any optimizations done to either system A nor system B. Cheers, Flo -- 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/