[PATCH RESEND v2] acpi-cpufreq: make the freq_table store the same freq value
ACPI's P-states will report the acpi_processor_px *states to acpi-cpufreq.
When the states likes these:
[index:freq, 0:2400 1:2400 2:2000 3:1600...],
we will initialize the freq_tables to those:
[index:driver_data:freq, 0:0:2400, 1:2:2000 2:3,1600 ... CPUFREQ_TABLE_END]
So when set the freqs to 2000, the data->acpi_data->state is 2
(data->freq_table[1].driver_data), So when call get_cur_freq_on_cpu, we get
the freqs is data->freq_table[2].frequency,the value is 1600.
we can make the freq_table store the same value to fix this case problem.
Signed-off-by: Wang Weidong
---
Change note:
v2: to check weather the freq_table will be changeable and clarify the problem.
The set of available states which come from acpi won't change. Just like
the power would be remove, the acpi driver will do that:
->acpi_processor_ppc_has_changed
->cpufreq_update_policy
->acpi_ppc_notifier_block.notifier_call
->acpi_processor_ppc_notifier
->cpufreq_verify_within_limits
The progress will change the policy's min_freq and max_freq
while it won't change the set of states(freq_tables).
---
drivers/cpufreq/acpi-cpufreq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/acpi-cpufreq.c b/drivers/cpufreq/acpi-cpufreq.c
index b0c18ed..93634a4 100644
--- a/drivers/cpufreq/acpi-cpufreq.c
+++ b/drivers/cpufreq/acpi-cpufreq.c
@@ -779,7 +779,7 @@ static int acpi_cpufreq_cpu_init(struct cpufreq_policy
*policy)
/* table init */
for (i = 0; i < perf->state_count; i++) {
- if (i > 0 && perf->states[i].core_frequency >=
+ if (i > 0 && perf->states[i].core_frequency >
data->freq_table[valid_states-1].frequency / 1000)
continue;
--
1.7.12
.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[PATCH RESEND v2] acpi-cpufreq: make the freq_table store the same freq value
ACPI's P-states will report the acpi_processor_px *states to acpi-cpufreq.
When the states likes these:
[index:freq, 0:2400 1:2400 2:2000 3:1600...],
we will initialize the freq_tables to those:
[index:driver_data:freq, 0:0:2400, 1:2:2000 2:3,1600 ... CPUFREQ_TABLE_END]
So when set the freqs to 2000, the data-acpi_data-state is 2
(data-freq_table[1].driver_data), So when call get_cur_freq_on_cpu, we get
the freqs is data-freq_table[2].frequency,the value is 1600.
we can make the freq_table store the same value to fix this case problem.
Signed-off-by: Wang Weidong wangweido...@huawei.com
---
Change note:
v2: to check weather the freq_table will be changeable and clarify the problem.
The set of available states which come from acpi won't change. Just like
the power would be remove, the acpi driver will do that:
-acpi_processor_ppc_has_changed
-cpufreq_update_policy
-acpi_ppc_notifier_block.notifier_call
-acpi_processor_ppc_notifier
-cpufreq_verify_within_limits
The progress will change the policy's min_freq and max_freq
while it won't change the set of states(freq_tables).
---
drivers/cpufreq/acpi-cpufreq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/acpi-cpufreq.c b/drivers/cpufreq/acpi-cpufreq.c
index b0c18ed..93634a4 100644
--- a/drivers/cpufreq/acpi-cpufreq.c
+++ b/drivers/cpufreq/acpi-cpufreq.c
@@ -779,7 +779,7 @@ static int acpi_cpufreq_cpu_init(struct cpufreq_policy
*policy)
/* table init */
for (i = 0; i perf-state_count; i++) {
- if (i 0 perf-states[i].core_frequency =
+ if (i 0 perf-states[i].core_frequency
data-freq_table[valid_states-1].frequency / 1000)
continue;
--
1.7.12
.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
