Peter Zijlstra <peterz@xxxxxxxxxxxxx> writes: > On Thu, 2012-10-18 at 08:51 +0300, Felipe Balbi wrote: >> > So the primary question remains: is RT runtime supposed to include the >> > time spent suspended? I suspect not. >> >> you might be right there, though we need Thomas or Peter to answer :-s > > re, sorry both tglx and I have been traveling, he still is, I'm trying > to play catch-up :-) > > Anyway, yeah I'm somewhat surprised the clock is 'running' when the > machine isn't. From what I could gather, this is !x86 hardware, right? > > x86 explicitly makes sure our clocks are 'stopped' during suspend, see > commit cd7240c0b900eb6d690ccee088a6c9b46dae815a. > > Can you do something similar for ARM? So I did the same thing for my ARM SoC, and it definitley stops the RT throttling. However, it has the undesriable (IMO) side effect of making timed printk output rather unhelpful for debugging suspend/resume since printk time stays constant throughout suspend/resume no matter how long you sleep. :( So does that mean we have to choose between useful printk times during suspend/resume or functioning IRQ threads during suspend/resume ? Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
