linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Dietmar Eggemann <dietmar.eggemann@arm.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	linux@arm.linux.org.uk,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Juri Lelli <juri.lelli@arm.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Morten Rasmussen <morten.rasmussen@arm.com>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH v4 02/10] cpufreq: provide default frequency-invariance setter function
Date: Tue, 19 Sep 2017 11:39:17 -0700	[thread overview]
Message-ID: <20170919183917.GC2792@ubuntu> (raw)
In-Reply-To: <20170825143206.30467-3-dietmar.eggemann@arm.com>

On 25-08-17, 15:31, Dietmar Eggemann wrote:
> Frequency-invariant accounting support based on the ratio of current
> frequency and maximum supported frequency is an optional feature an arch
> can implement.
> 
> Since there are cpufreq drivers (e.g. cpufreq-dt) which can be build for
> different arch's a default implementation of the frequency-invariance
> setter function arch_set_freq_scale() is needed.
> 
> This default implementation is an empty weak function which will be
> overwritten by a strong function in case the arch provides one.
> 
> The setter function passes the cpumask of related (to the frequency
> change) cpus (online and offline cpus), the (new) current frequency and
> the maximum supported frequency.
> 
> Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
> Cc: Viresh Kumar <viresh.kumar@linaro.org>
> Signed-off-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
> ---
>  drivers/cpufreq/cpufreq.c | 6 ++++++
>  include/linux/cpufreq.h   | 3 +++
>  2 files changed, 9 insertions(+)

Acked-by: Viresh Kumar <viresh.kumar@linaro.org>

-- 
viresh

  parent reply	other threads:[~2017-09-19 18:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25 14:31 [PATCH v4 00/10] arm, arm64, cpufreq: frequency- and cpu-invariant accounting support for task scheduler Dietmar Eggemann
2017-08-25 14:31 ` [PATCH v4 01/10] drivers base/arch_topology: free cpumask cpus_to_visit Dietmar Eggemann
2017-08-25 14:31 ` [PATCH v4 02/10] cpufreq: provide default frequency-invariance setter function Dietmar Eggemann
2017-09-07 23:22   ` Rafael J. Wysocki
2017-09-19 18:39   ` Viresh Kumar [this message]
2017-08-25 14:31 ` [PATCH v4 03/10] cpufreq: arm_big_little: invoke " Dietmar Eggemann
2017-08-25 14:32 ` [PATCH v4 04/10] cpufreq: dt: " Dietmar Eggemann
2017-08-25 14:32 ` [PATCH v4 05/10] drivers base/arch_topology: provide frequency-invariant accounting support Dietmar Eggemann
2017-08-25 14:32 ` [PATCH v4 06/10] drivers base/arch_topology: allow inlining cpu-invariant " Dietmar Eggemann
2017-08-25 14:32 ` [PATCH v4 07/10] arm: wire frequency-invariant accounting support up to the task scheduler Dietmar Eggemann
2017-08-25 14:32 ` [PATCH v4 08/10] arm: wire cpu-invariant " Dietmar Eggemann
2017-08-25 14:32 ` [PATCH v4 09/10] arm64: wire frequency-invariant " Dietmar Eggemann
2017-08-25 14:32 ` [PATCH v4 10/10] arm64: wire cpu-invariant " Dietmar Eggemann
2017-08-30 23:34 ` [PATCH v4 00/10] arm, arm64, cpufreq: frequency- and cpu-invariant accounting support for " Rafael J. Wysocki
2017-08-31 11:27   ` Dietmar Eggemann
2017-09-07 12:04     ` Dietmar Eggemann

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=20170919183917.GC2792@ubuntu \
    --to=viresh.kumar@linaro.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=juri.lelli@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=morten.rasmussen@arm.com \
    --cc=peterz@infradead.org \
    --cc=rjw@rjwysocki.net \
    --cc=sudeep.holla@arm.com \
    --cc=vincent.guittot@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;
as well as URLs for NNTP newsgroup(s).