mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Xiongfeng Wang <wangxiongfeng2@huawei.com>
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>
Subject: Re: [PATCH v2 0/2] Work around for Hisilicon CPPC cpufreq
Date: Thu, 14 Feb 2019 21:27:04 +0800	[thread overview]
Message-ID: <851b2825-3324-cfc4-0806-d4aa7ef577cd@huawei.com> (raw)
In-Reply-To: <2f397788-fcb0-a781-c497-9e698494f508@huawei.com>



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


      reply	other threads:[~2019-02-14 13:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-14  7:46 Xiongfeng Wang
2019-02-14  7:46 ` [PATCH v2 1/2] ACPI / CPPC: Add a helper to get desired performance Xiongfeng Wang
2019-02-14 10:42   ` Rafael J. Wysocki
2019-02-14  7:46 ` [PATCH v2 2/2] cpufreq / cppc: Work around for Hisilicon CPPC cpufreq Xiongfeng Wang
2019-02-14 10:58   ` Rafael J. Wysocki
2019-02-14 13:58     ` Xiongfeng Wang
2019-02-14 23:15       ` Rafael J. Wysocki
2019-02-15  1:25         ` Xiongfeng Wang
2019-02-15  9:28           ` Rafael J. Wysocki
2019-02-14 12:16   ` John Garry
2019-02-14 11:39 ` [PATCH v2 0/2] " John Garry
2019-02-14 13:27   ` Xiongfeng Wang [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=851b2825-3324-cfc4-0806-d4aa7ef577cd@huawei.com \
    --to=wangxiongfeng2@huawei.com \
    --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 \
    /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®