RE: omap3 pm: dependency between opp layer and cpufreq

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

 



> -----Original Message-----
> From: Premi, Sanjeev
> Sent: Thursday, May 27, 2010 10:30 PM

[...]

> >
> > 3) Was there any specific need to tie the functions "opp_get_voltage"
> and others to cpufreq only?
> 
> yes, because without cpufreq there is no transitions in the system :)
> 
> [sp] I does - via bootarg - mpurate!
> 
> When kernel boots, volatge must be set properly.
> We cannot rely on u-boot to be settiing everything correctly. e.g. 720MHz
> on OMAP3530 would fail at nominal 1.2V set by u-boot.

I agree, but mpurate does not seem to use the cpufreq interfaces - so is 
kinda a question how it interfaces back -> but note, mpurate tells us what
the start freq is for the system - it still does no *dynamic* transitions - 
just a static startup frequency. But I agree, it assumes that if you provide 
mpurate, the system supposedly is operating at that frequency, aka all
setups have been done for that operational frequency(including voltage)


Regards,
Nishanth Menon
--
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