On Thu, Aug 05, 2010 at 06:01:24PM -0700, david@lang.hm wrote:
quoted text
> On Thu, 5 Aug 2010, Brian Swetland wrote:

quoted text
>> 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).

quoted text
> does this then mean that you have multiple variations of suspend?

quoted text
> 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).
--
unsubscribe notice
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/