[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2f397788-fcb0-a781-c497-9e698494f508@huawei.com>
Date: Thu, 14 Feb 2019 11:39:22 +0000
From: John Garry <john.garry@...wei.com>
To: Xiongfeng Wang <wangxiongfeng2@...wei.com>,
<viresh.kumar@...aro.org>, <rafael@...nel.org>,
<gcherianv@...il.com>, <pprakash@...eaurora.org>,
<george.cherian@...ium.com>, <robert.moore@...el.com>
CC: <linux-acpi@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<guohanjun@...wei.com>
Subject: Re: [PATCH v2 0/2] Work around for Hisilicon CPPC cpufreq
On 14/02/2019 07:46, 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.
>
It would be convenient for reviewers to detail what changed between
versions in future.
John
> 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 | 38 +++++++++++++++++++++++
> drivers/cpufreq/cppc_cpufreq.c | 70 ++++++++++++++++++++++++++++++++++++++++++
> include/acpi/cppc_acpi.h | 1 +
> 3 files changed, 109 insertions(+)
>
Powered by blists - more mailing lists