From: Gautham R.Shenoy <gautham.shenoy@amd.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Perry Yuan <perry.yuan@amd.com>, <linux-pm@vger.kernel.org>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Artem S . Tashkinov" <aros@gmx.com>
Subject: Re: [PATCH] cpufreq: amd-pstate: Allow users to write 'default' EPP string
Date: Fri, 21 Jun 2024 14:13:38 +0530 [thread overview]
Message-ID: <877ceivg79.fsf@BLR-5CG11610CF.amd.com> (raw)
In-Reply-To: <20240612145737.1618-1-mario.limonciello@amd.com>
Mario Limonciello <mario.limonciello@amd.com> writes:
> The EPP string for 'default' represents what the firmware had configured
> as the default EPP value but once a user changes EPP to another string
> they can't reset it back to 'default'.
>
> Cache the firmware EPP value and allow the user to write 'default' using
> this value.
>
> Reported-by: Artem S. Tashkinov <aros@gmx.com>
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=217931#c61
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Reviewed-by: Gautham R. Shenoy <gautham.shenoy@amd.com>
> ---
> drivers/cpufreq/amd-pstate.c | 8 +++-----
> drivers/cpufreq/amd-pstate.h | 1 +
> 2 files changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/cpufreq/amd-pstate.c b/drivers/cpufreq/amd-pstate.c
> index fda8f86c90e0..5bdcdd3ea163 100644
> --- a/drivers/cpufreq/amd-pstate.c
> +++ b/drivers/cpufreq/amd-pstate.c
> @@ -282,10 +282,8 @@ static int amd_pstate_set_energy_pref_index(struct amd_cpudata *cpudata,
> int epp = -EINVAL;
> int ret;
>
> - if (!pref_index) {
> - pr_debug("EPP pref_index is invalid\n");
> - return -EINVAL;
> - }
> + if (!pref_index)
> + epp = cpudata->epp_default;
>
> if (epp == -EINVAL)
> epp = epp_values[pref_index];
> @@ -1441,7 +1439,7 @@ static int amd_pstate_epp_cpu_init(struct cpufreq_policy *policy)
>
> policy->driver_data = cpudata;
>
> - cpudata->epp_cached = amd_pstate_get_epp(cpudata, 0);
> + cpudata->epp_cached = cpudata->epp_default = amd_pstate_get_epp(cpudata, 0);
>
> policy->min = policy->cpuinfo.min_freq;
> policy->max = policy->cpuinfo.max_freq;
> diff --git a/drivers/cpufreq/amd-pstate.h b/drivers/cpufreq/amd-pstate.h
> index e6a28e7f4dbf..f80b33fa5d43 100644
> --- a/drivers/cpufreq/amd-pstate.h
> +++ b/drivers/cpufreq/amd-pstate.h
> @@ -99,6 +99,7 @@ struct amd_cpudata {
> u32 policy;
> u64 cppc_cap1_cached;
> bool suspended;
> + s16 epp_default;
> };
>
> #endif /* _LINUX_AMD_PSTATE_H */
> --
> 2.43.0
prev parent reply other threads:[~2024-06-21 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 14:57 [PATCH] cpufreq: amd-pstate: Allow users to write 'default' EPP string Mario Limonciello
2024-06-12 15:03 ` Artem S. Tashkinov
2024-06-13 9:21 ` Yuan, Perry
2024-06-21 8:43 ` Gautham R.Shenoy [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=877ceivg79.fsf@BLR-5CG11610CF.amd.com \
--to=gautham.shenoy@amd.com \
--cc=aros@gmx.com \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=perry.yuan@amd.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;
as well as URLs for NNTP newsgroup(s).