* [PATCH] cpufreq: get the cur_freq from acpi_processor_performance
@ 2014-08-01 9:52 Wang Weidong
0 siblings, 0 replies; only message in thread
From: Wang Weidong @ 2014-08-01 9:52 UTC (permalink / raw)
To: rjw, viresh.kumar; +Cc: linux-pm, linux-kernel@vger.kernel.org, wangweidong
As the initialized freq_tables maybe different from the p-states
values, so the array index is different as well.
p-states value: [2400 2400 2000 ...], while the freq_tables:
[2400 2000 ... CPUFREQ_TABLE_END]. After setted the freqs 2000,
the perf->state is 3 while the freqs_table's index should be 2.
So when call the get_cur_freq_on_cpu, the freqs value we get
is 2400.
So, fix the problem with the correct tables.
Signed-off-by: Wang Weidong <wangweidong1@huawei.com>
---
drivers/cpufreq/acpi-cpufreq.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/cpufreq/acpi-cpufreq.c b/drivers/cpufreq/acpi-cpufreq.c
index b0c18ed..2b934cb 100644
--- a/drivers/cpufreq/acpi-cpufreq.c
+++ b/drivers/cpufreq/acpi-cpufreq.c
@@ -365,6 +365,7 @@ static u32 get_cur_val(const struct cpumask *mask)
static unsigned int get_cur_freq_on_cpu(unsigned int cpu)
{
struct acpi_cpufreq_data *data = per_cpu(acfreq_data, cpu);
+ struct acpi_processor_performance *perf;
unsigned int freq;
unsigned int cached_freq;
@@ -375,7 +376,8 @@ static unsigned int get_cur_freq_on_cpu(unsigned int cpu)
return 0;
}
- cached_freq = data->freq_table[data->acpi_data->state].frequency;
+ perf = data->acpi_data;
+ cached_freq = perf->states[perf->state].core_frequency * 1000;
freq = extract_freq(get_cur_val(cpumask_of(cpu)), data);
if (freq != cached_freq) {
/*
--
1.7.12
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2014-08-01 9:53 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-08-01 9:52 [PATCH] cpufreq: get the cur_freq from acpi_processor_performance Wang Weidong
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).