>From Andy: CPU_FREQ does seem to work / work better at least on linux-linaro-2.6.39 on OMAP4 / Panda.
>From Vishwa: There was an issue in Clock framework due to which Core DVFS in OMAP3 was not fully functional. This problem is fixed by below commit id in mainline and same is present in .39 linaro kernel. Patch details: commit 5fd2a84ab3c8b87176e25db1d98c5cc34043a669 Author: Avinash H.M <[email protected]> Date: Mon May 9 12:29:40 2011 +0000 OMAP3: set the core dpll clk rate in its set_rate function 2.6.39 does not seem to have basic DVFS code that was pushed in 2.6.38 kernel. So CPUFREQ will not work on 2.6.39. I will pull this patch onto 2.6.38 linaro kernel and test cpufreq. -- You received this bug notification because you are a member of Linaro Release Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/784176 Title: CPU_FREQ support is broken for OMAP 3 and OMAP 4 Status in Linaro Linux: Confirmed Status in “linux-linaro-omap” package in Ubuntu: Confirmed Status in “linux-ti-omap4” package in Ubuntu: Confirmed Bug description: Current both Nicolas and Andy's kernel tree (2.6.38) is lacking proper support for CPU_FREQ. On OMAP 4 it tries to change the frequencies for the first CPU, and on OMAP 3 is basically freezes when calling cpufreq-info, besides not having a proper frequency scaling. The workaround now for the linux-linaro-omap kernel is to disable CPU_FREQ, so this bug is basically to track why it's currently disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/linux-linaro/+bug/784176/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~linaro-release Post to : [email protected] Unsubscribe : https://launchpad.net/~linaro-release More help : https://help.launchpad.net/ListHelp
