From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Alexey Zagorodnikov <xglooom@gmail.com>
Cc: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
platform-driver-x86@vger.kernel.org,
Hans de Goede <hansg@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] platform/x86/amd/pmf: Introduce option to disable Smart PC function in PMF
Date: Mon, 19 Jan 2026 12:13:49 +0200 (EET) [thread overview]
Message-ID: <fcb61ed2-72f9-c78d-855b-f446873e54e6@linux.intel.com> (raw)
In-Reply-To: <1eff30f0-f619-419b-ab26-b8c68cad87df@gmail.com>
On Sun, 18 Jan 2026, Alexey Zagorodnikov wrote:
> Sorry for the inconvenience, it is my first time :)
>
> Originally bugreport here https://gitlab.freedesktop.org/drm/amd/-/issues/4868
When the issue is reported in some tracker, the usual custom is to add
a Link tag to the changelog so it will be recorded with the change into
the kernel history.
--
i.
> But it turned out to be not a real bug, but rather a feature of the firmware,
> which in my case is not desirable. Would nice to have a toggle to disable,
> instead of completely blacklist module.
>
> Should I send v2 patch with a new message?
>
> On 1/18/26 20:20, Shyam Sundar S K wrote:
> >
> > On 1/18/2026 01:38, Alexey Zagorodnikov wrote:
> > > Signed-off-by: Alexey Zagorodnikov <xglooom@gmail.com>
> > Please include the context in the commit message instead of the cover
> > letter. Additionally, if there are any bug reports or issue tracker
> > entries (e.g., Bugzilla) documenting the problem this addresses,
> > please reference them to provide justification for the change.
> >
> > Thanks,
> > Shyam
> >
> > > ---
> > > drivers/platform/x86/amd/pmf/core.c | 19 ++++++++++++++-----
> > > 1 file changed, 14 insertions(+), 5 deletions(-)
> > >
> > > diff --git a/drivers/platform/x86/amd/pmf/core.c
> > > b/drivers/platform/x86/amd/pmf/core.c
> > > index 8fc293c9c5380..00a4fc899c727 100644
> > > --- a/drivers/platform/x86/amd/pmf/core.c
> > > +++ b/drivers/platform/x86/amd/pmf/core.c
> > > @@ -53,6 +53,11 @@ static bool force_load;
> > > module_param(force_load, bool, 0444);
> > > MODULE_PARM_DESC(force_load, "Force load this driver on supported older
> > > platforms (experimental)");
> > > +/* Force to disable Smart PC Solution */
> > > +static bool disable_smart_pc;
> > > +module_param(disable_smart_pc, bool, 0444);
> > > +MODULE_PARM_DESC(disable_smart_pc, "Disable Smart PC Solution");
> > > +
> > > static int amd_pmf_pwr_src_notify_call(struct notifier_block *nb,
> > > unsigned long event, void *data)
> > > {
> > > struct amd_pmf_dev *pmf = container_of(nb, struct amd_pmf_dev,
> > > pwr_src_notifier);
> > > @@ -362,11 +367,15 @@ static void amd_pmf_init_features(struct amd_pmf_dev
> > > *dev)
> > > dev_dbg(dev->dev, "SPS enabled and Platform Profiles
> > > registered\n");
> > > }
> > > - amd_pmf_init_smart_pc(dev);
> > > - if (dev->smart_pc_enabled) {
> > > - dev_dbg(dev->dev, "Smart PC Solution Enabled\n");
> > > - /* If Smart PC is enabled, no need to check for other features
> > > */
> > > - return;
> > > + if (disable_smart_pc) {
> > > + dev->smart_pc_enabled = false;
> > > + } else {
> > > + amd_pmf_init_smart_pc(dev);
> > > + if (dev->smart_pc_enabled) {
> > > + dev_dbg(dev->dev, "Smart PC Solution Enabled\n");
> > > + /* If Smart PC is enabled, no need to check for other
> > > features */
> > > + return;
> > > + }
> > > }
> > > if (is_apmf_func_supported(dev, APMF_FUNC_AUTO_MODE)) {
> >
>
next prev parent reply other threads:[~2026-01-19 10:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-17 20:08 [PATCH 0/1] " Alexey Zagorodnikov
2026-01-17 20:08 ` [PATCH 1/1] " Alexey Zagorodnikov
2026-01-18 15:20 ` Shyam Sundar S K
2026-01-18 17:58 ` Alexey Zagorodnikov
2026-01-19 10:13 ` Ilpo Järvinen [this message]
2026-01-19 10:00 ` [PATCH 0/1] " Ilpo Järvinen
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=fcb61ed2-72f9-c78d-855b-f446873e54e6@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=xglooom@gmail.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
Powered by JetHome