From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Leo Yan <leo.yan@linaro.org>,
Brendan Jackman <brendan.jackman@arm.com>,
linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org,
Amit Kucheria <amit.kucheria@linaro.org>
Subject: Re: [PATCH] cpufreq: dt: Set default policy->transition_delay_ns
Date: Tue, 27 Jun 2017 02:15:12 +0200 [thread overview]
Message-ID: <1537403.PHBCuCX8Fr@aspire.rjw.lan> (raw)
In-Reply-To: <20170522112727.GI6510@vireshk-i7>
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 a/kernel/sched/cpufreq_schedutil.c b/kernel/sched/cpufreq_schedutil.c
> > index 76877a6..dcc90fc 100644
> > --- a/kernel/sched/cpufreq_schedutil.c
> > +++ b/kernel/sched/cpufreq_schedutil.c
> > @@ -538,7 +538,7 @@ static int sugov_init(struct cpufreq_policy *policy)
> > unsigned int lat;
> >
> > tunables->rate_limit_us = LATENCY_MULTIPLIER;
> > - lat = policy->cpuinfo.transition_latency / NSEC_PER_USEC;
> > + lat = policy->cpuinfo.transition_latency / NSEC_PER_MSEC;
> > if (lat)
> > tunables->rate_limit_us *= lat;
> > }
>
> I will let Rafael comment in as well. NSEC_PER_USEC is used in the
> earlier governors as well (ondemand/conservative) in exactly the same
> way as schedutil is using.
The reason why it is used by schedutil is because the other governors used it
that way. IOW, doesn't matter. :-)
Thanks,
Rafael
next prev parent reply other threads:[~2017-06-27 0:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 5:10 [PATCH] cpufreq: dt: Set default policy->transition_delay_ns Viresh Kumar
2017-05-22 10:45 ` Brendan Jackman
2017-05-22 10:55 ` Viresh Kumar
2017-05-22 11:17 ` Leo Yan
2017-05-22 11:27 ` Viresh Kumar
2017-06-27 0:15 ` Rafael J. Wysocki [this message]
2017-06-27 4:20 ` Viresh Kumar
2017-06-27 16:08 ` Rafael J. Wysocki
2017-06-28 4:14 ` Viresh Kumar
2017-06-28 20:52 ` Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1537403.PHBCuCX8Fr@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=amit.kucheria@linaro.org \
--cc=brendan.jackman@arm.com \
--cc=leo.yan@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox