On Thu, 7 Jun 2012, Rajendra Nayak wrote:
> On Thursday 07 June 2012 11:43 AM, Paul Walmsley wrote:
> > Until the OMAP4 code is converted to disable the use of the clock
> > framework-based clockdomain enable/disable sequence, any clock used as
> > a hwmod main_clk must have a clockdomain associated with it. This
> > patch populates some clock structure clockdomain names to resolve the
> > following warnings during kernel init:
>
> But these associations are useless if the clock is not a 'gate' clock,
> except for getting rid of these warnings. Maybe we should make hwmod
> understand that not all clocks need to have a clockdomain associated
> with it and stop complaining.
In retrospect, I think I should have made clockdomains mandatory for all
clocks for OMAP4 back then, rather than only allowing them for some
clocks. As I understand it, that would have saved a lot of time and
debugging frustration on the bug fixed by commit
6c4a057bffe9823221eab547e11fac181dc18a2b ("ARM: OMAP4: clock data: Force a
DPLL clkdm/pwrdm ON before a relock"). Oh well.
- 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
