Messages in this thread | | | Date | Mon, 10 Jul 2017 12:10:10 +0530 | From | Viresh Kumar <> | Subject | Re: [PATCH v2 02/10] cpufreq: provide data for frequency-invariant load-tracking support |
| |
On 07-07-17, 17:01, Dietmar Eggemann wrote: > diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c > index 9bf97a366029..77c4d5e7a598 100644 > --- a/drivers/cpufreq/cpufreq.c > +++ b/drivers/cpufreq/cpufreq.c > @@ -301,6 +301,12 @@ static void adjust_jiffies(unsigned long val, struct cpufreq_freqs *ci) > #endif > } > > +#ifndef arch_set_freq_scale > +static void arch_set_freq_scale(struct cpumask *cpus, unsigned long cur_freq, > + unsigned long max_freq) > +{} > +#endif > + > static void __cpufreq_notify_transition(struct cpufreq_policy *policy, > struct cpufreq_freqs *freqs, unsigned int state) > { > @@ -343,6 +349,8 @@ static void __cpufreq_notify_transition(struct cpufreq_policy *policy, > CPUFREQ_POSTCHANGE, freqs); > if (likely(policy) && likely(policy->cpu == freqs->cpu)) > policy->cur = freqs->new; > + arch_set_freq_scale(policy->related_cpus, policy->cur, > + policy->cpuinfo.max_freq);
This function gets called for-each-cpu-in-policy, so you don't need the first argument. And the topology code already has max_freq, so not sure if you need the last parameter as well, specially for the ARM solution.
-- viresh
| |