From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: New feature proposal "quickwakeup" Date: Fri, 6 Nov 2009 17:03:21 +0000 Message-ID: <20091106170321.GA24312@srcf.ucam.org> References: <1257523241.1318.367.camel@xhp836-11> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cavan.codon.org.uk ([93.93.128.6]:44411 "EHLO cavan.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757641AbZKFRDV (ORCPT ); Fri, 6 Nov 2009 12:03:21 -0500 Content-Disposition: inline In-Reply-To: <1257523241.1318.367.camel@xhp836-11> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Falempe Jocelyn Cc: linux-acpi@vger.kernel.org, linux-omap@vger.kernel.org Hmm. This is an interesting approach. Just to understand the usecase better, though - my understanding is that Nokia's approach on Omap-based devices has been to treat "suspend" as a runtime state, without actually performing a systemwide transition. What are the constraints that make shifting into a different hardware state more efficient for you? -- Matthew Garrett | mjg59@srcf.ucam.org