From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 6) Date: Fri, 14 May 2010 09:18:15 -0700 Message-ID: <87fx1uo3so.fsf@deeprootsystems.com> References: <20100513191717.GA3428@atomide.com> <20100513214739.GM3428@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: (Magnus Damm's message of "Fri\, 14 May 2010 12\:25\:26 +0900") Sender: linux-kernel-owner@vger.kernel.org To: Magnus Damm Cc: Tony Lindgren , Alan Stern , Paul Walmsley , Arve =?iso-8859-1?Q?Hj=F8nnev=E5g?= , Linux-pm mailing list , Kernel development list , Tejun Heo , Oleg Nesterov , Theodore Ts'o , mark gross , Arjan van de Ven , Geoff Smith , Brian Swetland , "Rafael J. Wysocki" , Matthew Garrett , =?iso-8859-1?Q?Beno=EEt?= Cousson , linux-omap@vger.kernel.org, Vitaly Wool , Linus Walleij , Mark Brown , Liam Girdwood List-Id: linux-omap@vger.kernel.org Magnus Damm writes: > Still not sure how the system wide suspend is different from Runtime > PM and CPUidle from the hardware perspective... At least on OMAP and other embedded SoCs I'm familiar with, there is no difference from the hardware perspecitve. However, I understand that on ACPI-based systems, there are low-power that are only reachable via system-wide suspsend since ACPI does not provide the kernel with fine-grained control to hit those states during idle. That being said, I don't think this should be an issue since opportunistic suspend is currently targetted primarily at embedded HW which has much more fine-grained power control than traditional ACPI-based systems. To me the only real difference between system-wide suspend and runtime PM + CPUidle is the freezing of userspace. As has been discussed elsewhere in this discussion, any alternative solution must address the freezing/idling of userspace. Kevin