From: Nicholas Krause <xerofoify@gmail.com>
To: rjw@rjwysocki.net
Cc: viresh.kumar@linaro.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] cpufreq: Fix latency for cpufreq_info
Date: Mon, 14 Jul 2014 01:01:44 -0400 [thread overview]
Message-ID: <1405314104-9688-1-git-send-email-xerofoify@gmail.com> (raw)
This fixes the latency for the cpufreq policy to 1 million nanoseconds
that calls the function pxa_cpu_init for the member of the structure
called cpuinfo.transition_latency.
Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
---
drivers/cpufreq/pxa2xx-cpufreq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/pxa2xx-cpufreq.c b/drivers/cpufreq/pxa2xx-cpufreq.c
index e24269a..e08bb98 100644
--- a/drivers/cpufreq/pxa2xx-cpufreq.c
+++ b/drivers/cpufreq/pxa2xx-cpufreq.c
@@ -372,7 +372,7 @@ static int pxa_cpufreq_init(struct cpufreq_policy *policy)
init_sdram_rows();
/* set default policy and cpuinfo */
- policy->cpuinfo.transition_latency = 1000; /* FIXME: 1 ms, assumed */
+ policy->cpuinfo.transition_latency = 1000, 000;
/* Generate pxa25x the run cpufreq_frequency_table struct */
for (i = 0; i < NUM_PXA25x_RUN_FREQS; i++) {
--
1.9.1
next reply other threads:[~2014-07-14 5:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 5:01 Nicholas Krause [this message]
2014-07-14 6:10 ` [PATCH] cpufreq: Fix latency for cpufreq_info Viresh Kumar
2014-07-14 6:25 ` Nick Krause
-- strict thread matches above, loose matches on Subject: below --
2014-07-14 6:28 Nicholas Krause
2014-07-14 6:30 ` Viresh Kumar
2014-07-25 5:36 ` pramod gurav
2014-07-25 23:06 ` Nick Krause
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=1405314104-9688-1-git-send-email-xerofoify@gmail.com \
--to=xerofoify@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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;
as well as URLs for NNTP newsgroup(s).