On Tue, Mar 26, 2013 at 12:10:19AM +0100, Stephen Warren wrote: > From: Stephen Warren <swarren@xxxxxxxxxx> > > The Tegra clock driver is initialized during the ARM machine descriptor's > .init_irq() hook. It can't be initialized earlier, since dynamic memory > usage is required. It can't be initialized later, since the .init_timer() > hook needs the clocks initialized. However, at this time, udelay() > doesn't work. > > The Tegra clock initialization table may enable some PLLs. Enabling a PLL > may require usage of udelay(). Hence, this can't happen right when the > clock driver is initialized. > > To solve this, separate the clock driver initialization from the clock > table processing, so they can execute at separate times. > > Signed-off-by: Stephen Warren <swarren@xxxxxxxxxx> > --- > Peter, if this makes sense to you, perhaps you could included it at the > start of your CCF V9 (with the Tegra114 parts split out into the relevant > changes of yours). This looks good. I will take this into CCF v9. Thanks, Peter. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
