Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753825Ab0FFIUY (ORCPT ); Sun, 6 Jun 2010 04:20:24 -0400 Received: from smtp-out.google.com ([216.239.44.51]:61787 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752260Ab0FFIUU convert rfc822-to-8bit (ORCPT ); Sun, 6 Jun 2010 04:20:20 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:date:message-id:subject:from:to: cc:content-type:content-transfer-encoding; b=cia73hv1DgapKy1mHKrtKntrAOcr+8WzFKZH1MRdXCrmervi7YKSgeZyuwENOFOFM ttw6o3gLf16xRspCmAuww== MIME-Version: 1.0 In-Reply-To: References: <20100603193045.GA7188@elte.hu> <20100603231153.GA11302@elte.hu> <20100603232302.GA16184@elte.hu> <20100604071354.GA14451@elte.hu> <20100604083423.GD15181@elte.hu> <1275653210.27810.39762.camel@twins> <1275731653.27810.41078.camel@twins> <20100605092851.6ee15f13@infradead.org> Date: Sun, 6 Jun 2010 01:20:16 -0700 Message-ID: Subject: Re: [linux-pm] suspend blockers & Android integration From: Brian Swetland To: Vitaly Wool Cc: =?UTF-8?B?QXJ2ZSBIasO4bm5ldsOlZw==?= , Arjan van de Ven , tytso@mit.edu, Florian Mickler , 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 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1335 Lines: 27 On Sun, Jun 6, 2010 at 12:52 AM, Vitaly Wool wrote: > 2010/6/5 Arve Hjønnevåg : >> >> We clearly have different standards for what we consider good. We >> measure time suspended in minutes or hours, not seconds, and waking up >> every second or two causes a noticeable decrease in battery life on >> the hardware we have today. > > Are you stating that the existing Android implementation enters the > suspended state for hours for any of the existing designs? It varies depending on device and usage. The battery monitoring on NexusOne happens every ten minutes, so that's the longest you'll see a N1 suspended for. On a G1 or Dream/myTouch you can see 20-30 minutes between wakeups (depending on network issues and background data sync traffic), and if you have background data sync off those devices can sit in suspend for days at a time (unless you receive a phone call or something). In "airplane mode", with no local alarms, a device can easily sit in the lowest power state for a month or so, until the battery finally runs out. Brian -- 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/