Re: [PATCH 3/6] cpufreq: governor: Drop min_sampling_rate

2017-07-02 Thread Dominik Brodowski
On Fri, Jun 30, 2017 at 11:10:33AM +0530, Viresh Kumar wrote: > On 30-06-17, 06:53, Dominik Brodowski wrote: > > On Fri, Jun 30, 2017 at 09:04:25AM +0530, Viresh Kumar wrote: > > > On 29-06-17, 20:01, Dominik Brodowski wrote: > > > > On Thu, Jun 29, 2017 at 04:29:06PM +0530, Viresh Kumar wrote: >

Re: [PATCH 3/6] cpufreq: governor: Drop min_sampling_rate

2017-07-02 Thread Dominik Brodowski
On Fri, Jun 30, 2017 at 11:10:33AM +0530, Viresh Kumar wrote: > On 30-06-17, 06:53, Dominik Brodowski wrote: > > On Fri, Jun 30, 2017 at 09:04:25AM +0530, Viresh Kumar wrote: > > > On 29-06-17, 20:01, Dominik Brodowski wrote: > > > > On Thu, Jun 29, 2017 at 04:29:06PM +0530, Viresh Kumar wrote: >

Re: [PATCH 3/6] cpufreq: governor: Drop min_sampling_rate

2017-06-29 Thread Viresh Kumar
On 30-06-17, 06:53, Dominik Brodowski wrote: > On Fri, Jun 30, 2017 at 09:04:25AM +0530, Viresh Kumar wrote: > > On 29-06-17, 20:01, Dominik Brodowski wrote: > > > On Thu, Jun 29, 2017 at 04:29:06PM +0530, Viresh Kumar wrote: > > > > The cpufreq core and governors aren't supposed to set a limit on

Re: [PATCH 3/6] cpufreq: governor: Drop min_sampling_rate

2017-06-29 Thread Viresh Kumar
On 30-06-17, 06:53, Dominik Brodowski wrote: > On Fri, Jun 30, 2017 at 09:04:25AM +0530, Viresh Kumar wrote: > > On 29-06-17, 20:01, Dominik Brodowski wrote: > > > On Thu, Jun 29, 2017 at 04:29:06PM +0530, Viresh Kumar wrote: > > > > The cpufreq core and governors aren't supposed to set a limit on

Re: [PATCH 3/6] cpufreq: governor: Drop min_sampling_rate

2017-06-29 Thread Dominik Brodowski
On Fri, Jun 30, 2017 at 09:04:25AM +0530, Viresh Kumar wrote: > On 29-06-17, 20:01, Dominik Brodowski wrote: > > On Thu, Jun 29, 2017 at 04:29:06PM +0530, Viresh Kumar wrote: > > > The cpufreq core and governors aren't supposed to set a limit on how > > > fast we want to try changing the

Re: [PATCH 3/6] cpufreq: governor: Drop min_sampling_rate

2017-06-29 Thread Dominik Brodowski
On Fri, Jun 30, 2017 at 09:04:25AM +0530, Viresh Kumar wrote: > On 29-06-17, 20:01, Dominik Brodowski wrote: > > On Thu, Jun 29, 2017 at 04:29:06PM +0530, Viresh Kumar wrote: > > > The cpufreq core and governors aren't supposed to set a limit on how > > > fast we want to try changing the

Re: [PATCH 3/6] cpufreq: governor: Drop min_sampling_rate

2017-06-29 Thread Viresh Kumar
On 29-06-17, 20:01, Dominik Brodowski wrote: > On Thu, Jun 29, 2017 at 04:29:06PM +0530, Viresh Kumar wrote: > > The cpufreq core and governors aren't supposed to set a limit on how > > fast we want to try changing the frequency. This is currently done for > > the legacy governors with help of

Re: [PATCH 3/6] cpufreq: governor: Drop min_sampling_rate

2017-06-29 Thread Viresh Kumar
On 29-06-17, 20:01, Dominik Brodowski wrote: > On Thu, Jun 29, 2017 at 04:29:06PM +0530, Viresh Kumar wrote: > > The cpufreq core and governors aren't supposed to set a limit on how > > fast we want to try changing the frequency. This is currently done for > > the legacy governors with help of

Re: [PATCH 3/6] cpufreq: governor: Drop min_sampling_rate

2017-06-29 Thread Dominik Brodowski
On Thu, Jun 29, 2017 at 04:29:06PM +0530, Viresh Kumar wrote: > The cpufreq core and governors aren't supposed to set a limit on how > fast we want to try changing the frequency. This is currently done for > the legacy governors with help of min_sampling_rate. > > At worst, we may end up setting

Re: [PATCH 3/6] cpufreq: governor: Drop min_sampling_rate

2017-06-29 Thread Dominik Brodowski
On Thu, Jun 29, 2017 at 04:29:06PM +0530, Viresh Kumar wrote: > The cpufreq core and governors aren't supposed to set a limit on how > fast we want to try changing the frequency. This is currently done for > the legacy governors with help of min_sampling_rate. > > At worst, we may end up setting

[PATCH 3/6] cpufreq: governor: Drop min_sampling_rate

2017-06-29 Thread Viresh Kumar
The cpufreq core and governors aren't supposed to set a limit on how fast we want to try changing the frequency. This is currently done for the legacy governors with help of min_sampling_rate. At worst, we may end up setting the sampling rate to a value lower than the rate at which frequency can

[PATCH 3/6] cpufreq: governor: Drop min_sampling_rate

2017-06-29 Thread Viresh Kumar
The cpufreq core and governors aren't supposed to set a limit on how fast we want to try changing the frequency. This is currently done for the legacy governors with help of min_sampling_rate. At worst, we may end up setting the sampling rate to a value lower than the rate at which frequency can