lkml.org 
[lkml]   [2017]   [Jul]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Date
SubjectRe: [RFC V2 1/6] cpufreq: Replace "max_transition_latency" with "dynamic_switching"
On Thu, Jul 13, 2017 at 7:40 AM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> There is no limitation in the ondemand or conservative governors which
> disallow the transition_latency to be greater than 10 ms.
>
> The max_transition_latency field is rather used to disallow automatic
> dynamic frequency switching for platforms which didn't wanted these
> governors to run.
>
> Replace max_transition_latency with a boolean (dynamic_switching) and
> check for transition_latency == CPUFREQ_ETERNAL along with that. This
> makes it pretty straight forward to read/understand now.

Well, using CPUFREQ_ETERNAL for that on the driver side is still not
particularly straightforward IMO, so maybe add a
"no_dynamic_switching" to the driver structure and set it to "true"
for the one driver in question?

Thanks,
Rafael

\
 
 \ /
  Last update: 2017-07-13 18:20    [W:0.145 / U:0.176 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site