From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Corey Hickey <bugfood-ml@fatooh.org>
Cc: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH] platform/x86/amd/pmc: Detect when STB is not available
Date: Fri, 25 Oct 2024 17:55:47 +0300 (EEST) [thread overview]
Message-ID: <d8734a53-23d7-65b8-d632-1884814f181f@linux.intel.com> (raw)
In-Reply-To: <20241025051141.924760-1-bugfood-ml@fatooh.org>
On Thu, 24 Oct 2024, Corey Hickey wrote:
> From: Corey Hickey <bugfood-c@fatooh.org>
>
> Loading the amd_pmc module as:
>
> amd_pmc enable_stb=1
>
> ...can result in the following messages in the kernel ring buffer:
>
> amd_pmc AMDI0009:00: SMU cmd failed. err: 0xff
> ioremap on RAM at 0x0000000000000000 - 0x0000000000ffffff
> WARNING: CPU: 10 PID: 2151 at arch/x86/mm/ioremap.c:217 __ioremap_caller+0x2cd/0x340
>
> Additional debug shows that this happens when the calls to obtain
> S2D_PHYS_ADDR_LOW and S2D_PHYS_ADDR_HIGH return 0.
>
> Per discussion on platform-driver-x86@vger.kernel.org, this condition
> indicates that the STB is not available.
If you want to refer to discussion, add it into a Link: tag. Only write
the conclusion into the commit message (the part you have there after
comma).
> In order to avoid the ioremap warning, and to help the user understand
> the situation, catch the invalid address and print an error.
>
> Signed-off-by: Corey Hickey <bugfood-c@fatooh.org>
Isn't Fixes tag appropriate for this change?
> ---
> drivers/platform/x86/amd/pmc/pmc.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/platform/x86/amd/pmc/pmc.c b/drivers/platform/x86/amd/pmc/pmc.c
> index bbb8edb62e00..72b1dfc64bf1 100644
> --- a/drivers/platform/x86/amd/pmc/pmc.c
> +++ b/drivers/platform/x86/amd/pmc/pmc.c
> @@ -998,6 +998,11 @@ static int amd_pmc_s2d_init(struct amd_pmc_dev *dev)
> amd_pmc_send_cmd(dev, S2D_PHYS_ADDR_LOW, &phys_addr_low, dev->s2d_msg_id, true);
> amd_pmc_send_cmd(dev, S2D_PHYS_ADDR_HIGH, &phys_addr_hi, dev->s2d_msg_id, true);
>
> + if (!phys_addr_hi && !phys_addr_low) {
> + dev_err(dev->dev, "amd_pmc: STB is not enabled on the system; disable enable_stb or contact system vendor\n");
Won't that end up duplicating the prefix if you put one into the string?
The prefix is handled for you by pr_fmt() which is already provided in
this file.
--
i.
> + return -EINVAL;
> + }
> +
> stb_phys_addr = ((u64)phys_addr_hi << 32 | phys_addr_low);
>
> /* Clear msg_port for other SMU operation */
>
next prev parent reply other threads:[~2024-10-25 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 5:11 [PATCH] platform/x86/amd/pmc: Detect when STB is not available Corey Hickey
2024-10-25 14:55 ` Ilpo Järvinen [this message]
2024-10-27 2:34 ` Corey Hickey
2024-10-27 2:34 ` [PATCH v2] " Corey Hickey
2024-10-28 3:55 ` Shyam Sundar S K
2024-10-28 18:03 ` Corey Hickey
2024-10-28 18:02 ` [PATCH v3] " Corey Hickey
2024-10-29 12:17 ` Ilpo Järvinen
2024-11-04 10:21 ` Hans de Goede
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=d8734a53-23d7-65b8-d632-1884814f181f@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=bugfood-ml@fatooh.org \
--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