Hi Mike, On Mon, 30 Jul 2012, Turquette, Mike wrote: > On Mon, Jul 30, 2012 at 3:31 PM, Paul Walmsley <paul@xxxxxxxxx> wrote: > > > So if we make a change like this one, it seems like we would basically > > expect it to break once we start doing anything meaningful with > > clk_prepare(), like using clk_prepare() for voltage scaling or > > something that requires I2C? We'd also probably want to mark this > > with some kind of "HACK" comment. > > Did you have anything in mind to start using clk_prepare? I still hope > to get rid of it some day and replace that call with a combination of > clk_enable and a check like clk_enable_can_sleep. Nothing that requires immediate attention. Mostly am just trying to think through how to reconcile the clock and device management code that we have with what other SoC programmers are apparently implementing in their platform code. - 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
