Enclosed please find the link to the Weekly Status report & meeting minutes for the Power Management working group for the week ending 2011-12-09
== Weekly Status Report == https://wiki.linaro.org/WorkingGroups/PowerManagement/Status/2011-12-08
== Meeting Minutes == https://wiki.linaro.org/WorkingGroups/PowerManagement/Meetings/2011-12-07
== Summary == (For details, see the Weekly Status Report and Meeting Minutes )
* Linaro Connect http://connect.linaro.org/events/event/lcq1-12/ initial session blueprints are set: https://blueprints.launchpad.net/sprints/lcq1-12?searchtext=power-management
* Common Clock * Implemented notification will push the patches next. * Discussion on going about where the common struct code will reside, looks like it may stay in the kernel source while the binding code will be in the DT.
* Cpuidle * Submitted a patch for common ARM cpuidle patch * Submitted v4 patches for exynos4210 cpuidle support with Russell fixes.
* Sched_mc * Preparing a new version of sched_mc for ARM * Working on submitting a patch on scheduler and cpu_power, which has been accepted into Nico Linaro-kernel tree
* Thermal Management * Tested that temperature is reduced in production using the current solution-done on Origen board. * Added and posted the patch for a new trip type needed for cooling devices like cpufreq. * Working on adding a generic processor cooling devices(non ACPI based, for ACPI already exists). * Continue to work on i.MX6 cpufreq and thermal solution.
Best regards, Mounir
I saw a topic 'Multi-core decision co-ordination' at https://wiki.linaro.org/WorkingGroups/PowerManagement/Doc/CPUFreq . Is it still going on?
Thanks Richard
On Sat, Dec 10, 2011 at 6:59 AM, Richard Zhao richard.zhao@linaro.org wrote:
I saw a topic 'Multi-core decision co-ordination' at https://wiki.linaro.org/WorkingGroups/PowerManagement/Doc/CPUFreq . Is it still going on?
Richard,
This was related to teaching cpufreq to synchronise the scaling of frequency on both cores in case of a hardware constraint. But that is already taken care of by the cpufreq core (affected_cpus, related_cpus)
Regards, Amit
Hi Amit,
On 12 December 2011 15:21, Amit Kucheria amit.kucheria@linaro.org wrote:
On Sat, Dec 10, 2011 at 6:59 AM, Richard Zhao richard.zhao@linaro.org wrote:
I saw a topic 'Multi-core decision co-ordination' at https://wiki.linaro.org/WorkingGroups/PowerManagement/Doc/CPUFreq . Is it still going on?
Richard,
This was related to teaching cpufreq to synchronise the scaling of frequency on both cores in case of a hardware constraint. But that is already taken care of by the cpufreq core (affected_cpus, related_cpus)
policy->shared_type = CPUFREQ_SHARED_TYPE_ANY; cpumask_setall(policy->cpus); Do you mean add above to cpufreq_driver.init ? When suspend/resume, cpufreq_driver.init/exit also be called multi times, though finally only cpu0 inited.
Thanks Richard
Regards, Amit