From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Hans de Goede <hansg@kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:X86 PLATFORM DRIVERS"
<platform-driver-x86@vger.kernel.org>,
Francis De Brabandere <francisdb@gmail.com>
Subject: Re: [PATCH 3/4] platform/x86/amd/pmc: Do not fail probe when STB init fails
Date: Tue, 21 Jul 2026 13:29:25 +0300 (EEST) [thread overview]
Message-ID: <03684762-b5f7-a48b-33a6-0c5aff345d6a@linux.intel.com> (raw)
In-Reply-To: <20260717162023.956346-4-mario.limonciello@amd.com>
On Fri, 17 Jul 2026, Mario Limonciello wrote:
> STB (Spill to DRAM) is an optional debugging facility that is only
> enabled through the enable_stb module parameter. On some platforms the
One whitespace is enough.
> SMU refuses the S2D setup outright, and on long-running systems the large
> telemetry region can fail to ioremap. In either case amd_stb_s2d_init()
> returns an error and, because probe treated that as fatal, the entire
> PMC driver failed to load - silently disabling s0i3 support even though
There's odd change to past tense here.
treated -> treats
failed -> fails
> STB is only a debug aid.
>
> Downgrade the failure to a warning and continue probing so that s0i3
> support via the LPS0 handler no longer depends on an optional debug
> feature.
>
> Since probe no longer aborts on this path, the LPS0 and debugfs
> unwinding added by the earlier fix in this series becomes unreachable
> and is removed.
>
> Assisted-by: Claude:opus
> Reported-by: Francis De Brabandere <francisdb@gmail.com>
> Closes: https://bugzilla.kernel.org/show_bug.cgi?id=221759
> Tested-by: Francis De Brabandere <francisdb@gmail.com>
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
> drivers/platform/x86/amd/pmc/pmc.c | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/platform/x86/amd/pmc/pmc.c b/drivers/platform/x86/amd/pmc/pmc.c
> index 630a664bdd2f4..5b6c90abd4e5f 100644
> --- a/drivers/platform/x86/amd/pmc/pmc.c
> +++ b/drivers/platform/x86/amd/pmc/pmc.c
> @@ -917,19 +917,24 @@ static int amd_pmc_probe(struct platform_device *pdev)
> }
>
> amd_pmc_dbgfs_register(dev);
> +
> + /*
> + * STB is an optional debugging facility, only enabled via the
> + * enable_stb module parameter. A failure to initialize it (e.g. the
> + * SMU refusing the request, or the telemetry region failing to map)
> + * must not prevent the rest of the driver - most importantly the s0i3
> + * LPS0 handler - from working, so treat it as non-fatal.
> + */
> err = amd_stb_s2d_init(dev);
> if (err)
> - goto err_dbgfs_unregister;
> + dev_warn(dev->dev, "STB initialization failed (%d), continuing without STB support\n",
> + err);
Please add include.
>
> if (IS_ENABLED(CONFIG_AMD_MP2_STB))
> amd_mp2_stb_init(dev);
> pm_report_max_hw_sleep(U64_MAX);
> return 0;
>
> -err_dbgfs_unregister:
> - amd_pmc_dbgfs_unregister(dev);
> - if (IS_ENABLED(CONFIG_SUSPEND))
> - acpi_unregister_lps0_dev(&amd_pmc_s2idle_dev_ops);
> err_pci_dev_put:
> pci_dev_put(rdev);
> return err;
>
--
i.
next prev parent reply other threads:[~2026-07-21 10:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 16:20 [PATCH 0/4] Some fixes for amd-pmc handling of the STB Mario Limonciello
2026-07-17 16:20 ` [PATCH 1/4] platform/x86/amd/pmc: Fix LPS0 and debugfs leaks when STB init fails Mario Limonciello
2026-07-21 10:19 ` Ilpo Järvinen
2026-07-17 16:20 ` [PATCH 2/4] platform/x86/amd/pmc: Fix error handling in amd_stb_s2d_init() Mario Limonciello
2026-07-21 10:24 ` Ilpo Järvinen
2026-07-17 16:20 ` [PATCH 3/4] platform/x86/amd/pmc: Do not fail probe when STB init fails Mario Limonciello
2026-07-21 10:29 ` Ilpo Järvinen [this message]
2026-07-17 16:20 ` [PATCH 4/4] platform/x86/amd/pmc: Validate S2D physical address before ioremap Mario Limonciello
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=03684762-b5f7-a48b-33a6-0c5aff345d6a@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=francisdb@gmail.com \
--cc=hansg@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=platform-driver-x86@vger.kernel.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
all inboxes | Powered by JetHome®