Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: [PATCH v2 0/2] Work around for Hisilicon CPPC cpufreq
To:     John Garry <john.garry@huawei.com>, <viresh.kumar@linaro.org>,
        <rafael@kernel.org>, <gcherianv@gmail.com>,
        <pprakash@codeaurora.org>, <george.cherian@cavium.com>,
        <robert.moore@intel.com>
CC:     <linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
        <guohanjun@huawei.com>
References: <1550130368-60513-1-git-send-email-wangxiongfeng2@huawei.com>
 <2f397788-fcb0-a781-c497-9e698494f508@huawei.com>
From:   Xiongfeng Wang <wangxiongfeng2@huawei.com>
Message-ID: <851b2825-3324-cfc4-0806-d4aa7ef577cd@huawei.com>
Date:   Thu, 14 Feb 2019 21:27:04 +0800
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <2f397788-fcb0-a781-c497-9e698494f508@huawei.com>
Content-Type: text/plain; charset="windows-1252"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


On 2019/2/14 19:39, John Garry wrote:
> 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.

Thanks, I will add changelog next time.

Xiongfeng

> 
> 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(+)
>>
> 
> 
> 
> .
>