RE: Omap3 omap3_clk_lock_dpll5() problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Gadiyar, Anand wrote:
> Arno Steffen wrote:
> > 
> > I do have some messages while booting a 2.6.33 kernel:
> > 
> > What does this mean? How can I get rid of it?
> > What is omap3_clk_lock_dpll5()  doing and what if I comment it out? I
> > guess it make some sense ;)
> > 
> 
> Not sure why you have this issue - I'll have to dig a bit, or maybe other
> people can comment. But I can tell  you what this function is for.
> 

Looking at the 2.6.33 code, I see the WARN_ON comes from this code fragment:


                /* No freqsel on OMAP4 */
                if (!cpu_is_omap44xx()) {
                        freqsel = _omap3_dpll_compute_freqsel(clk,
                                                dd->last_rounded_n);
                        if (!freqsel)
                                WARN_ON(1);
                }

So, _omap3_dpll_compute_freqsel() returned 0.

Can you send me a kernel log with the keyword "debug" added to the bootargs?

Thanks,
Anand
--
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


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux