Searched hist:c17495b01b72b53bd290f442d39b060e015c7aea (Results 1 – 2 of 2) sorted by relevance
/openbmc/linux/include/linux/ |
H A D | cpufreq.h | diff c17495b01b72b53bd290f442d39b060e015c7aea Tue Aug 10 01:34:33 CDT 2021 Viresh Kumar <viresh.kumar@linaro.org> cpufreq: Add callback to register with energy model
Many cpufreq drivers register with the energy model for each policy and do exactly the same thing. Follow the footsteps of thermal-cooling, to get it done from the cpufreq core itself.
Provide a new callback, which will be called, if present, by the cpufreq core at the right moment (more on that in the code's comment). Also provide a generic implementation that uses dev_pm_opp_of_register_em().
This also allows us to register with the EM at a later point of time, compared to ->init(), from where the EM core can access cpufreq policy directly using cpufreq_cpu_get() type of helpers and perform other work, like marking few frequencies inefficient, this will be done separately.
Reviewed-by: Quentin Perret <qperret@google.com> Reviewed-by: Lukasz Luba <lukasz.luba@arm.com> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
|
/openbmc/linux/drivers/cpufreq/ |
H A D | cpufreq.c | diff c17495b01b72b53bd290f442d39b060e015c7aea Tue Aug 10 01:34:33 CDT 2021 Viresh Kumar <viresh.kumar@linaro.org> cpufreq: Add callback to register with energy model
Many cpufreq drivers register with the energy model for each policy and do exactly the same thing. Follow the footsteps of thermal-cooling, to get it done from the cpufreq core itself.
Provide a new callback, which will be called, if present, by the cpufreq core at the right moment (more on that in the code's comment). Also provide a generic implementation that uses dev_pm_opp_of_register_em().
This also allows us to register with the EM at a later point of time, compared to ->init(), from where the EM core can access cpufreq policy directly using cpufreq_cpu_get() type of helpers and perform other work, like marking few frequencies inefficient, this will be done separately.
Reviewed-by: Quentin Perret <qperret@google.com> Reviewed-by: Lukasz Luba <lukasz.luba@arm.com> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
|