[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1417142619-14548-1-git-send-email-wangweidong1@huawei.com>
Date: Fri, 28 Nov 2014 10:43:37 +0800
From: Wang Weidong <wangweidong1@...wei.com>
To: <rjw@...ysocki.net>, <viresh.kumar@...aro.org>
CC: <wangweidong1@...wei.com>, <linux-pm@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <guohanjun@...wei.com>
Subject: [PATCH 0/2] fix some problems for cpufreq
Hi Rafael and Viresh
Sorry to trouble you again. As for:
"acpi-cpufreq: get the cur_freq from acpi_processor_performance states"
I do it again, and add the other patch.
patch #1: acpi-cpufreq: make the freq_table store the same freq value
I think it can work. 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:
call
->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).
patch #2: cpufreq: show the real avail freqs with the freq_table
when the min_freq and max_freq change, we should sync the availble
freqs.
Regards,
Wang
Wang Weidong (2):
acpi-cpufreq: make the freq_table store the same freq value
cpufreq: show the real avail freqs with the freq_table
drivers/cpufreq/acpi-cpufreq.c | 2 +-
drivers/cpufreq/freq_table.c | 4 +++-
2 files changed, 4 insertions(+), 2 deletions(-)
--
1.7.12
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists