Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757215AbcJMVWO (ORCPT ); Thu, 13 Oct 2016 17:22:14 -0400 Received: from mail-vk0-f54.google.com ([209.85.213.54]:34699 "EHLO mail-vk0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755782AbcJMVWH (ORCPT ); Thu, 13 Oct 2016 17:22:07 -0400 MIME-Version: 1.0 In-Reply-To: References: <1476380015-21001-1-git-send-email-hotran@apm.com> From: Hoan Tran Date: Thu, 13 Oct 2016 14:21:18 -0700 Message-ID: Subject: Re: [PATCH v2] cpufreq: CPPC: Correct desired_perf calculation To: "Rafael J. Wysocki" Cc: "Prakash, Prashanth" , "Rafael J. Wysocki" , Viresh Kumar , Al Stone , Linux PM , Linux Kernel Mailing List , Loc Ho , Duc Dang , Christopher Covington Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 821 Lines: 27 On Thu, Oct 13, 2016 at 2:12 PM, Rafael J. Wysocki wrote: > On Thu, Oct 13, 2016 at 9:37 PM, Prakash, Prashanth > 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 >> Reviewed-by: Prashanth Prakash >> >> Hi Rafael, >> Can you please pick this one for 4.9, as it is bug fix? > > Sure, I will queue it up. > Thanks, Rafael and Prashanth ! Hoan > Thanks, > Rafael