On Thu, 8 Nov 2012, Mike Turquette wrote: > You're right. In my rush I glossed over the clkdm decrement part. In > light of the suspend/resume issues I'm not sure this approach is really > valid. I think getting to the bottom of those issues will give the > final word. What do you think about something like this? It's still under test and review here, but seems to avoid the warnings on 3530ES3 Beagle at least. The usage of __clk_get_enable_count() in this code still seems like a hack to me. It would be better for the CCF to call a different clk_hw_ops function pointer for the disable-unused-clocks case. But if you agree, and plan to fix this, or have some other cleaner fix in mind for the near future, then something like this seems reasonable for the short term to me. What do you think? - Paul -- 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
