From: "Gautham R. Shenoy" <gautham.shenoy@amd.com>
To: Huang Rui <ray.huang@amd.com>
Cc: "Karny, Wyes" <Wyes.Karny@amd.com>,
"Limonciello, Mario" <Mario.Limonciello@amd.com>,
"Yuan, Perry" <Perry.Yuan@amd.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpufreq/amd-pstate: Fix the return value of amd_pstate_fast_switch()
Date: Fri, 24 Nov 2023 15:55:25 +0530 [thread overview]
Message-ID: <ZWB6Fb3KcqC1fqbD@BLR-5CG11610CF.amd.com> (raw)
In-Reply-To: <ZWBRVlxBxb6DW+3P@amd.com>
On Fri, Nov 24, 2023 at 03:31:34PM +0800, Huang Rui wrote:
> On Fri, Nov 24, 2023 at 12:23:58PM +0800, Karny, Wyes wrote:
> > On 23 Nov 13:57, Gautham R. Shenoy wrote:
> > > cpufreq_driver->fast_switch() callback expects a frequency as a return
> > > value. amd_pstate_fast_switch() was returning the return value of
> > > amd_pstate_update_freq(), which only indicates a success or failure.
> > >
> > > Fix this by making amd_pstate_fast_switch() return the target_freq
> > > when the call to amd_pstate_update_freq() is successful, and return
> > > the current frequency from policy->cur when the call to
> > > amd_pstate_update_freq() is unsuccessful.
> > >
> > > Fixes: 4badf2eb1e98 ("cpufreq: amd-pstate: Add ->fast_switch() callback")
> >
> > Reviewed-by: Wyes Karny <wyes.karny@amd.com>
> >
>
> Acked-by: Huang Rui <ray.huang@amd.com>
Thanks!
>
> Do you want to cc stable mailing list to fix it in stable kernels?
Yes, I forgot to do that. I will send a v2 having collected your
Acked-by and the Reviewed-by's from Perry and Wyes.
>
> Thanks,
> Ray
--
Thanks and Regards
gautham.
prev parent reply other threads:[~2023-11-24 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 8:27 [PATCH] cpufreq/amd-pstate: Fix the return value of amd_pstate_fast_switch() Gautham R. Shenoy
2023-11-23 8:54 ` Yuan, Perry
2023-11-24 4:23 ` Wyes Karny
2023-11-24 7:31 ` Huang Rui
2023-11-24 10:25 ` 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=ZWB6Fb3KcqC1fqbD@BLR-5CG11610CF.amd.com \
--to=gautham.shenoy@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Perry.Yuan@amd.com \
--cc=Wyes.Karny@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=ray.huang@amd.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