RE: [PATCH F 06/12] OMAP2/3 clock: every clock must have a clkdm

2009-02-05 Thread Paul Walmsley
Hi Richard, On Tue, 3 Feb 2009, Woodruff, Richard wrote: > > Virtual clocks should soon be eliminated from the OMAP clock tree. ( > > "Virtual clocks" is here used to refer a clock that does not have a > > referent in the hardware; the usage of the term in the code is loose.) > > So far as I kno

RE: [PATCH F 06/12] OMAP2/3 clock: every clock must have a clkdm

2009-02-03 Thread Woodruff, Richard
> Virtual clocks should soon be eliminated from the OMAP clock tree. ( > "Virtual clocks" is here used to refer a clock that does not have a > referent in the hardware; the usage of the term in the code is loose.) > So far as I know, all of the OMAP virtual clocks have either turned out to > be su

Re: [PATCH F 06/12] OMAP2/3 clock: every clock must have a clkdm

2009-02-03 Thread Paul Walmsley
Hello Russell, On Sat, 31 Jan 2009, Russell King - ARM Linux wrote: > 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 clockd

Re: [PATCH F 06/12] OMAP2/3 clock: every clock must have a clkdm

2009-01-31 Thread Russell King - ARM Linux
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() h