Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933967Ab0HFMbe (ORCPT ); Fri, 6 Aug 2010 08:31:34 -0400 Received: from cassiel.sirena.org.uk ([80.68.93.111]:46575 "EHLO cassiel.sirena.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759313Ab0HFMbb (ORCPT ); Fri, 6 Aug 2010 08:31:31 -0400 Date: Fri, 6 Aug 2010 13:30:48 +0100 From: Mark Brown To: david@lang.hm Cc: Brian Swetland , paulmck@linux.vnet.ibm.com, kevin granade , Arve Hj?nnev?g , Matthew Garrett , "Rafael J. Wysocki" , Arjan van de Ven , linux-pm@lists.linux-foundation.org, linux-kernel@vger.kernel.org, pavel@ucw.cz, florian@mickler.org, stern@rowland.harvard.edu, peterz@infradead.org, tglx@linutronix.de, alan@lxorguk.ukuu.org.uk Subject: Re: Attempted summary of suspend-blockers LKML thread Message-ID: <20100806123047.GE31326@sirena.org.uk> References: <20100805203102.GN2447@linux.vnet.ibm.com> <20100805230304.GQ2447@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Cookie: No line available at 300 baud. User-Agent: Mutt/1.5.18 (2008-05-17) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: broonie@sirena.org.uk X-SA-Exim-Scanned: No (on cassiel.sirena.org.uk); SAEximRunCond expanded to false Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1446 Lines: 29 On Thu, Aug 05, 2010 at 06:01:24PM -0700, david@lang.hm wrote: > On Thu, 5 Aug 2010, Brian Swetland wrote: >> Obviously not all clocks are stopped (the DSP and codec are powered >> and clocked, for example), but yeah we can clock gate and power gate >> the cpu and most other peripherals while audio is playing on a number >> of ARM SoC designs available today (and the past few years). > does this then mean that you have multiple variations of suspend? > for example, one where the audio stuff is left powered, and one where it > isn't? This was the core of the issue I was raising in the last thread about this (the one following the rename to suspend blockers). Essentially what happens in a mainline context is that some subsystems can with varying degress of optionality ignore some or all of the instruction to suspend and keep bits of the system alive during suspend. Those that stay alive will either have per subsystem handling or will be outside the direct control of the kernel entirely (the modem is a good example of the latter case in many systems - in terms of the software it's essentially a parallel computer that's sitting in the system rather than a perhiperal of the AP). -- 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/