[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKohpo=t=HcOMHfG_wRhaPAucDsOCmW4wW9_UjPmv5uE29v36g@mail.gmail.com>
Date: Sat, 17 May 2014 09:36:33 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Stephen Warren <swarren@...dotorg.org>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>,
Lists linaro-kernel <linaro-kernel@...ts.linaro.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Arvind Chauhan <arvind.chauhan@....com>,
Stephen Warren <swarren@...dia.com>,
Nicolas Pitre <nicolas.pitre@...aro.org>,
Doug Anderson <dianders@...omium.org>,
Russell King - ARM Linux <linux@....linux.org.uk>,
Thomas Abraham <thomas.abraham@...aro.org>,
Peter De Schrijver <pdeschrijver@...dia.com>
Subject: Re: [PATCH V2 2/3] cpufreq: add support for intermediate (stable) frequencies
On 17 May 2014 00:20, Stephen Warren <swarren@...dotorg.org> wrote:
> s/Uset/Used.
:(
>> diff --git a/include/linux/cpufreq.h b/include/linux/cpufreq.h
>> + unsigned int (*get_intermediate)(struct cpufreq_policy *policy,
>> + unsigned int index);
>
> Should get_intermediate be passed a struct cpufreq_freqs freqs rather
> than just the target index? That way, if the intermediate frequency
> varies depending on old/new frequencies, then the driver won't have to
> go look up the current frequency in order to implement that logic.
That can be done by simply doing policy->cur and we don't require to
get it from hardware again. So, probably should stay as is.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists