From: Viresh Kumar <viresh.kumar@linaro.org>
To: Jacob Tanenbaum <jtanenba@redhat.com>
Cc: linux-pm@vger.kernel.org, corbet@lwn.net, rjw@rjwysocki.net,
prarit@redhat.com
Subject: Re: [PATCH] pcc-cpufreq driver update default value of cpuinfo_transition_latency
Date: Fri, 20 Nov 2015 07:28:20 +0530 [thread overview]
Message-ID: <20151120015820.GK3737@ubuntu> (raw)
In-Reply-To: <1447946941-14923-1-git-send-email-jtanenba@redhat.com>
On 19-11-15, 10:29, Jacob Tanenbaum wrote:
> The cpufreq documentation specifies
>
> policy->cpuinfo.transition_latency the time it takes on this CPU to
> switch between two frequencies in
> nanoseconds (if appropriate, else
> specify CPUFREQ_ETERNAL)
>
> currently pcc-cpufreq does not expose the value and sets it to zero. I
> changed the pcc-cpufreq driver and it's documentation to conform to the
> default value specified in Documentation/cpu-freq/cpu-drivers.txt
>
> Signed-off-by: Jacob Tanenbaum <jtanenba@redhat.com>
> ---
> Documentation/cpu-freq/pcc-cpufreq.txt | 4 ++--
> drivers/cpufreq/pcc-cpufreq.c | 2 ++
> 2 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/cpu-freq/pcc-cpufreq.txt b/Documentation/cpu-freq/pcc-cpufreq.txt
> index 9e3c3b3..0a94224 100644
> --- a/Documentation/cpu-freq/pcc-cpufreq.txt
> +++ b/Documentation/cpu-freq/pcc-cpufreq.txt
> @@ -159,8 +159,8 @@ to be strictly associated with a P-state.
>
> 2.2 cpuinfo_transition_latency:
> -------------------------------
> -The cpuinfo_transition_latency field is 0. The PCC specification does
> -not include a field to expose this value currently.
> +The cpuinfo_transition_latency field is CPUFREQ_ETERNAL. The PCC specification
> +does not include a field to expose this value currently.
>
> 2.3 cpuinfo_cur_freq:
> ---------------------
> diff --git a/drivers/cpufreq/pcc-cpufreq.c b/drivers/cpufreq/pcc-cpufreq.c
> index 2a0d589..808a320 100644
> --- a/drivers/cpufreq/pcc-cpufreq.c
> +++ b/drivers/cpufreq/pcc-cpufreq.c
> @@ -555,6 +555,8 @@ static int pcc_cpufreq_cpu_init(struct cpufreq_policy *policy)
> policy->min = policy->cpuinfo.min_freq =
> ioread32(&pcch_hdr->minimum_frequency) * 1000;
>
> + policy->cpuinfo.transition_latency = CPUFREQ_ETERNAL;
> +
> pr_debug("init: policy->max is %d, policy->min is %d\n",
> policy->max, policy->min);
> out:
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
next prev parent reply other threads:[~2015-11-20 1:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 15:29 [PATCH] pcc-cpufreq driver update default value of cpuinfo_transition_latency Jacob Tanenbaum
2015-11-20 1:58 ` Viresh Kumar [this message]
2015-12-14 23:57 ` 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=20151120015820.GK3737@ubuntu \
--to=viresh.kumar@linaro.org \
--cc=corbet@lwn.net \
--cc=jtanenba@redhat.com \
--cc=linux-pm@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.