On Thu, 2012-02-16 at 15:27 +0530, Shilimkar, Santosh wrote: > On Thu, Feb 16, 2012 at 2:27 PM, Tero Kristo <t-kristo@xxxxxx> wrote: > > On Wed, 2012-02-15 at 11:37 -0800, Kevin Hilman wrote: > >> Tero Kristo <t-kristo@xxxxxx> writes: > >> > >> > Attempting this will cause problems especially with off-mode enabled. > >> > >> Please be more verbose about the problems seen, and the root cause(s). > >> > > > > I was actually looking forward for some help with this commit message, > > as I am still not quite sure what is going on in here. :) Here is the > > log for suspend (btw, cam_pwrdm does not go to off in mainline yet, but > > I think that is probably fixed by the patch from Paul, > > omap_set_pwrdm_state() does not work properly.) The warning comes out > > after wakeup from off-mode, and it is triggered by the disabling of > > autodeps before off-mode entry. > > > This mostly indicates that one of the per clock-domain module > clock turning ON seems to be not working well with auto deps > disabled. This leads to interconnect violation. > > if not tried already, can you put the per_clockdomain in SW_WKUP > in the low power code early resume path and see if this > error goes away. This seems to get rid of the dump also. It looks like some driver resume is not behaving nicely, I am trying to pinpoint the culprit currently and see whether it can provide more info. -Tero -- 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
