Hello, On Thu, 5 Jun 2008, Igor Stoppa wrote:
> - if a dvfs change is responsible of changing the rate supplied to a > driver which asked it with clk_get_rate(), the dvfs transition has no > reason to happen in case it would violate the constraints set by clock > users. There aren't any such constraints in the current tree. clk_set_rate() is mostly only useful for code that doesn't expect the clock rate to be changed by other code. Pre- and post-clk-rate-change notifiers should fix this for code that does need to know clock rates precisely. - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
