* Tony Lindgren <tony@xxxxxxxxxxx> [200417 15:08]: > Maybe the PM runtime usecounts get unbalanced somewhere in the > driver where we end up with driver permanently in disabled state? Or it could be that with omap_hdq.c no longer blocking SoC deeper idle states, omap_hdq.c now loses context if you have omap3 off mode enabled during idle? If so, this can easily be fixed by adding a cpu_pm notifier along the lines of what we already have for few drivers: $ git grep -e CLUSTER_PM_ENTER -e CLUSTER_PM_EXIT Regards, Tony
