public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sibi Sankar <quic_sibis@quicinc.com>, Dhruva Gole <d-gole@ti.com>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	"Gautham R . Shenoy" <gautham.shenoy@amd.com>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Yipeng Zou <zouyipeng@huawei.com>,
	"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH v2 1/2] cpufreq: Allow drivers to advertise boost enabled
Date: Thu, 27 Jun 2024 14:11:53 -0500	[thread overview]
Message-ID: <5ed06d29-a8b6-48f6-b341-3cd32c19c8d7@amd.com> (raw)
In-Reply-To: <CAJZ5v0hu1rVOLycx5K4YWOGhtC8YfSYupc8D6qygtXVGtvxJrQ@mail.gmail.com>

On 6/27/2024 04:59, Rafael J. Wysocki wrote:
> On Wed, Jun 26, 2024 at 10:47 PM Mario Limonciello
> <mario.limonciello@amd.com> wrote:
>>
>> The behavior introduced in commit f37a4d6b4a2c ("cpufreq: Fix per-policy
>> boost behavior on SoCs using cpufreq_boost_set_sw()") sets up the boost
>> policy incorrectly when boost has been enabled by the platform firmware
>> initially even if a driver sets the policy up.
>>
>> This is because policy_has_boost_freq() assumes that there is a frequency
>> table set up by the driver and that the boost frequencies are advertised
>> in that table. This assumption doesn't work for acpi-cpufreq or
>> amd-pstate. Only use this check to enable boost if it's not already
>> enabled instead of also disabling it if alreayd enabled.
>>
>> Reviewed-by: Sibi Sankar <quic_sibis@quicinc.com>
>> Reviewed-by: Dhruva Gole <d-gole@ti.com>
>> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>> Reviewed-by: Gautham R. Shenoy <gautham.shenoy@amd.com>
>> Fixes: f37a4d6b4a2c ("cpufreq: Fix per-policy boost behavior on SoCs using cpufreq_boost_set_sw()")
> 
> CC: stable I suppose?

Yes, I didn't realize f37a4d6b4a2c came in 6.9, I had assumed it was 
6.10.  But since it's 6.9, yes if you can please add stable tag when 
committing.

> 
>> Suggested-by: Viresh Kumar <viresh.kumar@linaro.org>
>> Suggested-by: Gautham R. Shenoy <gautham.shenoy@amd.com>
>> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
>> ---
>> Cc: Sibi Sankar <quic_sibis@quicinc.com>
>> Cc: Dietmar Eggemann <dietmar.eggemann@arm.com>
>> Cc: Viresh Kumar <viresh.kumar@linaro.org>
>> Cc: Dhruva Gole <d-gole@ti.com>
>> Cc: Yipeng Zou <zouyipeng@huawei.com>
>> Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>> v1->v2
>>   * Pick up tags
>> ---
>>   drivers/cpufreq/cpufreq.c | 3 ++-
>>   1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
>> index 1fdabb660231..270ea04fb616 100644
>> --- a/drivers/cpufreq/cpufreq.c
>> +++ b/drivers/cpufreq/cpufreq.c
>> @@ -1430,7 +1430,8 @@ static int cpufreq_online(unsigned int cpu)
>>                  }
>>
>>                  /* Let the per-policy boost flag mirror the cpufreq_driver boost during init */
>> -               policy->boost_enabled = cpufreq_boost_enabled() && policy_has_boost_freq(policy);
>> +               if (cpufreq_boost_enabled() && policy_has_boost_freq(policy))
>> +                       policy->boost_enabled = true;
>>
>>                  /*
>>                   * The initialization has succeeded and the policy is online.
>> --


  reply	other threads:[~2024-06-27 19:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26 20:47 [PATCH v2 1/2] cpufreq: Allow drivers to advertise boost enabled Mario Limonciello
2024-06-26 20:47 ` [PATCH v2 2/2] cpufreq: acpi: Mark boost policy as enabled when setting boost Mario Limonciello
2024-06-27  5:17   ` Gautham R.Shenoy
2024-07-01  7:07   ` Viresh Kumar
2024-06-27  9:59 ` [PATCH v2 1/2] cpufreq: Allow drivers to advertise boost enabled Rafael J. Wysocki
2024-06-27 19:11   ` Mario Limonciello [this message]
2024-07-01 16:15     ` Rafael J. Wysocki

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=5ed06d29-a8b6-48f6-b341-3cd32c19c8d7@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=d-gole@ti.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=gautham.shenoy@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=quic_sibis@quicinc.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rafael@kernel.org \
    --cc=viresh.kumar@linaro.org \
    --cc=zouyipeng@huawei.com \
    /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