Re: [PATCH] cpufreq: dt: Set default policy->transition_delay_ns

2017-06-28 Thread Rafael J. Wysocki
On Wednesday, June 28, 2017 09:44:55 AM Viresh Kumar wrote: > On 27-06-17, 18:08, Rafael J. Wysocki wrote: > > On Tue, Jun 27, 2017 at 6:20 AM, Viresh Kumar > > wrote: > > > @Rafael: Will it be fine to lower down the value of LATENCY_MULTIPLIER? > > > > We can do that, but then I think we need t

Re: [PATCH] cpufreq: dt: Set default policy->transition_delay_ns

2017-06-27 Thread Viresh Kumar
On 27-06-17, 18:08, Rafael J. Wysocki wrote: > On Tue, Jun 27, 2017 at 6:20 AM, Viresh Kumar wrote: > > @Rafael: Will it be fine to lower down the value of LATENCY_MULTIPLIER? > > We can do that, but then I think we need to compensate for the change > in the old governors code or there may be sur

Re: [PATCH] cpufreq: dt: Set default policy->transition_delay_ns

2017-06-27 Thread Rafael J. Wysocki
Hi, On Tue, Jun 27, 2017 at 6:20 AM, Viresh Kumar wrote: > On 27-06-17, 02:15, Rafael J. Wysocki wrote: >> On Monday, May 22, 2017 04:57:27 PM Viresh Kumar wrote: >> > On 22-05-17, 19:17, Leo Yan wrote: >> > > This afternoon Amit pointed me for this patch, should fix as below? >> > > Otherwise it

Re: [PATCH] cpufreq: dt: Set default policy->transition_delay_ns

2017-06-26 Thread Viresh Kumar
On 27-06-17, 02:15, Rafael J. Wysocki wrote: > On Monday, May 22, 2017 04:57:27 PM Viresh Kumar wrote: > > On 22-05-17, 19:17, Leo Yan wrote: > > > This afternoon Amit pointed me for this patch, should fix as below? > > > Otherwise it seems directly assign the same value from unit 'ns' to > > > 'us

Re: [PATCH] cpufreq: dt: Set default policy->transition_delay_ns

2017-06-26 Thread Rafael J. Wysocki
On Monday, May 22, 2017 04:57:27 PM Viresh Kumar wrote: > On 22-05-17, 19:17, Leo Yan wrote: > > This afternoon Amit pointed me for this patch, should fix as below? > > Otherwise it seems directly assign the same value from unit 'ns' to > > 'us' but without any value conversion. > > > > diff --git

Re: [PATCH] cpufreq: dt: Set default policy->transition_delay_ns

2017-05-22 Thread Viresh Kumar
On 22-05-17, 19:17, Leo Yan wrote: > This afternoon Amit pointed me for this patch, should fix as below? > Otherwise it seems directly assign the same value from unit 'ns' to > 'us' but without any value conversion. > > diff --git a/kernel/sched/cpufreq_schedutil.c > b/kernel/sched/cpufreq_schedu

Re: [PATCH] cpufreq: dt: Set default policy->transition_delay_ns

2017-05-22 Thread Leo Yan
On Mon, May 22, 2017 at 04:25:22PM +0530, Viresh Kumar wrote: > On 22-05-17, 11:45, Brendan Jackman wrote: > > Hi Viresh, > > > > On Mon, May 22 2017 at 05:10, Viresh Kumar wrote: > > > The rate_limit_us for the schedutil governor is getting set to 500 ms by > > > default for the ARM64 hikey board

Re: [PATCH] cpufreq: dt: Set default policy->transition_delay_ns

2017-05-22 Thread Viresh Kumar
On 22-05-17, 11:45, Brendan Jackman wrote: > Hi Viresh, > > On Mon, May 22 2017 at 05:10, Viresh Kumar wrote: > > The rate_limit_us for the schedutil governor is getting set to 500 ms by > > default for the ARM64 hikey board. And its way too much, even for the > > default value. Lets set the defau

Re: [PATCH] cpufreq: dt: Set default policy->transition_delay_ns

2017-05-22 Thread Brendan Jackman
Hi Viresh, On Mon, May 22 2017 at 05:10, Viresh Kumar wrote: > The rate_limit_us for the schedutil governor is getting set to 500 ms by > default for the ARM64 hikey board. And its way too much, even for the > default value. Lets set the default transition_delay_ns to something > more realistic (1

[PATCH] cpufreq: dt: Set default policy->transition_delay_ns

2017-05-21 Thread Viresh Kumar
The rate_limit_us for the schedutil governor is getting set to 500 ms by default for the ARM64 hikey board. And its way too much, even for the default value. Lets set the default transition_delay_ns to something more realistic (10 ms), while the userspace always have a chance to set something it wa