Re: [RFC V2 1/6] cpufreq: Replace "max_transition_latency" with "dynamic_switching"

2017-07-17 Thread Rafael J. Wysocki
On Monday, July 17, 2017 05:28:51 PM Viresh Kumar wrote: > On 15-07-17, 14:26, Rafael J. Wysocki wrote: > > On Saturday, July 15, 2017 07:08:28 AM Dominik Brodowski wrote: > > > > Exactly. But lets take a quick look at the drivers ussing CPUFREQ_ETERNAL: > > > > > > Using CPUFREQ_ETERNAL, as poli

Re: [RFC V2 1/6] cpufreq: Replace "max_transition_latency" with "dynamic_switching"

2017-07-17 Thread Viresh Kumar
On 15-07-17, 14:26, Rafael J. Wysocki wrote: > On Saturday, July 15, 2017 07:08:28 AM Dominik Brodowski wrote: > > Exactly. But lets take a quick look at the drivers ussing CPUFREQ_ETERNAL: > > > > Using CPUFREQ_ETERNAL, as policy-setting drivers: > > > > - intel_pstate.c - for the intel_pstate

Re: [RFC V2 1/6] cpufreq: Replace "max_transition_latency" with "dynamic_switching"

2017-07-15 Thread Rafael J. Wysocki
On Saturday, July 15, 2017 07:08:28 AM Dominik Brodowski wrote: > On Sat, Jul 15, 2017 at 12:06:24AM +0200, Rafael J. Wysocki wrote: > > On Friday, July 14, 2017 01:11:58 PM Rafael J. Wysocki wrote: > > > On Fri, Jul 14, 2017 at 9:01 AM, Dominik Brodowski > > > wrote: > > > > On Thu, Jul 13, 2017

Re: [RFC V2 1/6] cpufreq: Replace "max_transition_latency" with "dynamic_switching"

2017-07-14 Thread Dominik Brodowski
On Sat, Jul 15, 2017 at 12:06:24AM +0200, Rafael J. Wysocki wrote: > On Friday, July 14, 2017 01:11:58 PM Rafael J. Wysocki wrote: > > On Fri, Jul 14, 2017 at 9:01 AM, Dominik Brodowski > > wrote: > > > On Thu, Jul 13, 2017 at 06:19:53PM +0200, Rafael J. Wysocki wrote: > > >> On Thu, Jul 13, 2017

Re: [RFC V2 1/6] cpufreq: Replace "max_transition_latency" with "dynamic_switching"

2017-07-14 Thread Rafael J. Wysocki
On Friday, July 14, 2017 01:11:58 PM Rafael J. Wysocki wrote: > On Fri, Jul 14, 2017 at 9:01 AM, Dominik Brodowski > wrote: > > On Thu, Jul 13, 2017 at 06:19:53PM +0200, Rafael J. Wysocki wrote: > >> On Thu, Jul 13, 2017 at 7:40 AM, Viresh Kumar > >> wrote: > >> > There is no limitation in the o

Re: [RFC V2 1/6] cpufreq: Replace "max_transition_latency" with "dynamic_switching"

2017-07-14 Thread Rafael J. Wysocki
On Fri, Jul 14, 2017 at 9:01 AM, Dominik Brodowski wrote: > On Thu, Jul 13, 2017 at 06:19:53PM +0200, Rafael J. Wysocki wrote: >> On Thu, Jul 13, 2017 at 7:40 AM, Viresh Kumar >> wrote: >> > There is no limitation in the ondemand or conservative governors which >> > disallow the transition_laten

Re: [RFC V2 1/6] cpufreq: Replace "max_transition_latency" with "dynamic_switching"

2017-07-14 Thread Dominik Brodowski
On Thu, Jul 13, 2017 at 06:19:53PM +0200, Rafael J. Wysocki wrote: > On Thu, Jul 13, 2017 at 7:40 AM, Viresh Kumar 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 fiel

Re: [RFC V2 1/6] cpufreq: Replace "max_transition_latency" with "dynamic_switching"

2017-07-13 Thread Rafael J. Wysocki
On Thu, Jul 13, 2017 at 7:40 AM, Viresh Kumar 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 plat

[RFC V2 1/6] cpufreq: Replace "max_transition_latency" with "dynamic_switching"

2017-07-12 Thread Viresh Kumar
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_