On Friday, August 26, 2011, Govindraj.R wrote: > Hello, > > During system_wide_suspend pm runtime is disabled. > I.e. __pm_runtime_disable is called from __device_suspend. > Now, if a wakeup interrupt is triggered and the wakeup device irq handler > is called even before device_resume and pm_runtime_enable happens, > the device irq_handler proceeds to enable clock with runtime API to > handle wakeup event. > > Wouldn't this result in system wide abort since the pm_runtime is not enabled > yet from dpm_resume? > As we end up accessing regs after doing runtime get_sync. > > Looks like this scenario is not handled currently. > Or Am I missing something here? To be precise, what do you mean by "wakeup interrupt"? Rafael -- 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
