[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0jiRwgRherPXDQoV8kCdDZrW-1sv4p92vs6zJiwn7f4tQ@mail.gmail.com>
Date: Thu, 13 Oct 2016 23:12:09 +0200
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: "Prakash, Prashanth" <pprakash@...eaurora.org>
Cc: Hoan Tran <hotran@....com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Viresh Kumar <viresh.kumar@...aro.org>,
Al Stone <ahs3@...hat.com>,
Linux PM <linux-pm@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
lho@....com, Duc Dang <dhdang@....com>,
Christopher Covington <cov@...eaurora.org>
Subject: Re: [PATCH v2] cpufreq: CPPC: Correct desired_perf calculation
On Thu, Oct 13, 2016 at 9:37 PM, Prakash, Prashanth
<pprakash@...eaurora.org> wrote:
> On 10/13/2016 11:33 AM, Hoan Tran wrote:
>> The desired_perf is an abstract performance number. Its value should
>> be in the range of [lowest perf, highest perf] of CPPC.
>> The correct calculation is
>> desired_perf = freq * cppc_highest_perf / cppc_dmi_max_khz
>>
>> And cppc_cpufreq_set_target() returns if desired_perf is exactly
>> the same with the old perf.
>>
>> Signed-off-by: Hoan Tran <hotran@....com>
> Reviewed-by: Prashanth Prakash <pprakash@...eaurora.org>
>
> Hi Rafael,
> Can you please pick this one for 4.9, as it is bug fix?
Sure, I will queue it up.
Thanks,
Rafael
Powered by blists - more mailing lists