From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Xiongfeng Wang <wangxiongfeng2@huawei.com>
Cc: viresh.kumar@linaro.org, rafael@kernel.org, gcherianv@gmail.com,
pprakash@codeaurora.org, george.cherian@cavium.com,
robert.moore@intel.com, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, guohanjun@huawei.com,
john.garry@huawei.com
Subject: Re: [PATCH v3 0/2] Work around for Hisilicon CPPC cpufreq
Date: Tue, 19 Feb 2019 10:59:00 +0100 [thread overview]
Message-ID: <12311117.DSx6JT7Gj8@aspire.rjw.lan> (raw)
In-Reply-To: <1550375655-58007-1-git-send-email-wangxiongfeng2@huawei.com>
On Sunday, February 17, 2019 4:54:13 AM CET Xiongfeng Wang wrote:
> Hisilicon chips do not support delivered performance counter register
> and reference performance counter register. But the platform can
> calculate the real performance using its own method. This patch provide
> a workaround for this problem, and other platforms can also use this
> workaround framework. We reuse the desired performance register to
> store the real performance calculated by the platform. After the
> platform finished the frequency adjust, it gets the real performance and
> writes it into desired performance register. OS can use it to calculate
> the real frequency.
>
> Changlog:
>
> v2 -> v3:
> Recontruct 'cppc_get_desired_perf'.
> Rename 'cppc_workaround_info' to 'cppc_workaround_oem_info'
> Drop 'get_rate' member from struct cppc_workaround_oem_info
> Change 'cppc_wa_get_rate' pointer to a flag to indicate whether
> we need to aplly the workaround.
> Move the new functions to the beginning of cppc-cpufreq.c
>
>
> Xiongfeng Wang (2):
> ACPI / CPPC: Add a helper to get desired performance
> cpufreq / cppc: Work around for Hisilicon CPPC cpufreq
>
> drivers/acpi/cppc_acpi.c | 39 +++++++++++++++++++++++++
> drivers/cpufreq/cppc_cpufreq.c | 66 ++++++++++++++++++++++++++++++++++++++++++
> include/acpi/cppc_acpi.h | 1 +
> 3 files changed, 106 insertions(+)
>
>
Both patches applied, thanks!
prev parent reply other threads:[~2019-02-19 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-17 3:54 Xiongfeng Wang
2019-02-17 3:54 ` [PATCH v3 1/2] ACPI / CPPC: Add a helper to get desired performance Xiongfeng Wang
2019-02-17 3:54 ` [PATCH v3 2/2] cpufreq / cppc: Work around for Hisilicon CPPC cpufreq Xiongfeng Wang
2019-02-19 9:59 ` Rafael J. Wysocki [this message]
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=12311117.DSx6JT7Gj8@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=gcherianv@gmail.com \
--cc=george.cherian@cavium.com \
--cc=guohanjun@huawei.com \
--cc=john.garry@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pprakash@codeaurora.org \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.com \
--cc=viresh.kumar@linaro.org \
--cc=wangxiongfeng2@huawei.com \
/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
all inboxes | Powered by JetHome®