Hello Thara, On Thu, 30 Sep 2010, Thara Gopinath wrote: > This patch extends the OMAP4 clock data to include > various x2 clock nodes as the clock framework > skips a *2 whie calculating the dpll locked frequency. > > Signed-off-by: Thara Gopinath <thara@xxxxxx> > Acked-by: Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> > --- > Currently the framework is extended to include x2 nodes > only for a few clocks critical for OMAP4 DVFS. This > exercise needs to be done for most of the other post divider > clocks as and when necessary. Benoît and I have been discussing this - I think we should probably fix this problem for all of the DPLLs and HSDIVIDERs in one patch. I'll let Benoît comment further, but I think the current plan will be to generate a CLKOUTX2 node after the DPLLs, and then to use that as the parent for the various HSDIVIDERs that use that X2 output. Also, I think we should make this change in a consistent way with regards to what the autogeneration scripts should generate. This way, we won't have to redo it later and cause unnecessary patch noise. Perhaps you can help Benoît update the autogeneration scripts for the above changes? - Paul
