On Wed, Jan 28, 2009 at 12:35:15PM -0700, Paul Walmsley wrote: > Every OMAP2/3 clock must now have an assigned clockdomain, so we can > remove the checks from clk_enable()/clk_disable(). Instead, verify > that the clockdomain is present only at clock init time via the > arch_clock clk_register() hook. I don't see the point of requiring all clocks to have a clockdomain field. Given that we have virtual clocks, it is quite reasonable for some clocks not to have a clock domain associated with them. The overhead for avoiding this requirement isn't that great, and I feel that there's little benefit from this change. -- 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
