On Thu, 26 Apr 2012, Hiremath, Vaibhav wrote:
> On Thu, Apr 26, 2012 at 14:27:20, Paul Walmsley wrote:
(attribution lost)
> > > I am thinking of separating clocktree patch (PATCH-V3 3/3) from this series,
> > > so that clockdomain stuff can get in independently, and clocktree anyway
> > > will follow them (it may take some time in review cycle).
> >
> > Yes, I was thinking of doing this too. The only aspect that gave me pause
> > is that the clockdomain changes are not 100% separate from the clock tree.
> > So we may have to update the clockdomain data as the clock tree changes.
>
> Why do you say that, clockdomain changes are not 100% separate from
> clocktree? It is completely independent...
Clock enables and disables call clkdm_clk_{enable,disable}() which
undertakes the clockdomain enable sequence on the first clock enabled
inside the clockdomain, and the clockdomain disable sequence on the last
clock inside the clockdomain. The clockdomain is associated with the
clock via the struct clk .clkdm and .clkdm_name fields.
So yes, they are interconnected; particularly if the clkdiv32k MODULEMODE
"clock" is really needed.
- 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
