RE: Multimachine uImage and cpufreq-cpu0/cpufreq-omap2 breakage

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

 



On Fri, Oct 19, 2012 at 12:10:51, AnilKumar, Chimata wrote:
> On Wed, Oct 17, 2012 at 15:48:22, Koen Kooi wrote:
> > Hi,
> > 
> > I'm currently building 3.7rc1 kernels meant to run on beagleboards (omap3), pandaboards (omap4) and beaglebones (am335x). At the moment I'm only testing it on beaglebone and I noticed a problem with the different cpufreq drivers getting in eachothers way.
> > 
> > I patched in cpufreq-cpu0 support for AM335x and that's was working great. After rebasing to 3.7-rc1 it stopped working because cpufreq-omap2 tried to load, failed and made the cpufreq-cpu0 driver error out. The workaround is simple: only enable on driver.
> > 
> > So my question is: Is this the intended behaviour? I would expect the cpufreq-omap2 driver to not load when booted on am335x using DT, but it is a persistent bugger.
> 
> Hi Koen,
> 
> AFAICS regulator_get() should return NULL if there is no "vcc" regulator
> node and should not proceed further but its proceeding and doing the
> cpufreq_register_driver(), so we are seeing failure for cpu0 driver
> after this.
> 
> clk_get() should be moved to omap_cpufreq_init to avoid this. (Extra
> protection).

This behavior is present in omap-cpufreq driver

> 
> Thanks
> AnilKumar
> 

--
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