From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
markgross@kernel.org, Sanket.Goswami@amd.com,
mario.limonciello@amd.com, platform-driver-x86@vger.kernel.org,
Mark Hasemeyer <markhas@chromium.org>
Subject: Re: [PATCH v2] platform/x86/amd/pmc: adjust amd_pmc_get_dram_size() behavior
Date: Mon, 13 Nov 2023 15:10:06 +0200 (EET) [thread overview]
Message-ID: <a7435bf5-4465-5835-9595-ab453c8f125c@linux.intel.com> (raw)
In-Reply-To: <20231109061709.2964246-1-Shyam-sundar.S-k@amd.com>
On Thu, 9 Nov 2023, Shyam Sundar S K wrote:
> After talking to the PMFW team, its understood that the "get dram size"
> mbox command would only be supported on specific platforms (like Mendocino)
> and not all. So adjust the behavior of amd_pmc_get_dram_size() function
> such that,
>
> - if that's Rembrandt or Mendocino and the underlying PMFW knows how
> to execute the "get dram size" command it shall give the custom dram size.
>
> - if the underlying FW does not report the dram size, we just proceed
> further and assign the default dram size.
This commit message lacks the description of the problem we have the Fixes
tag for. Please explain also that problem as it's very much related.
> Cc: Mark Hasemeyer <markhas@chromium.org>
Mark, does this patch solve the issue for you?
> Link: https://lore.kernel.org/platform-driver-x86/3b224c62-a1d8-41bd-aced-5825f5f20e66@amd.com/
> Fixes: be8325fb3d8c ("platform/x86/amd: pmc: Get STB DRAM size from PMFW")
> Suggested-by: Sanket Goswami <Sanket.Goswami@amd.com>
> Signed-off-by: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
> ---
>
> v2:
> - Based on review-ilpo branch
> - Drop calling get smu version from probe.
>
> drivers/platform/x86/amd/pmc/pmc.c | 11 +----------
> 1 file changed, 1 insertion(+), 10 deletions(-)
>
> diff --git a/drivers/platform/x86/amd/pmc/pmc.c b/drivers/platform/x86/amd/pmc/pmc.c
> index cd6ac04c1468..501c72c7d34c 100644
> --- a/drivers/platform/x86/amd/pmc/pmc.c
> +++ b/drivers/platform/x86/amd/pmc/pmc.c
> @@ -968,17 +968,8 @@ static int amd_pmc_get_dram_size(struct amd_pmc_dev *dev)
> {
> int ret;
>
> - switch (dev->cpu_id) {
> - case AMD_CPU_ID_YC:
> - if (!(dev->major > 90 || (dev->major == 90 && dev->minor > 39))) {
> - ret = -EINVAL;
> - goto err_dram_size;
> - }
> - break;
> - default:
> - ret = -EINVAL;
> + if (dev->cpu_id != AMD_CPU_ID_YC)
> goto err_dram_size;
This now ends up returning uninitialized ret variable. I'd have expected
compiler to warn you about it...??
It also still prints the dev_err() after jumping to the label. If we know
dram size not supported, dev_err is not really correct level (I'd say
dev_dbg at most but better would be to not print anything, IMO).
Thinking it more though, it would make more sense to initialize the
default dram_size within this function to make it easier to track the code
+ call this function amd_pmc_init_dram_size() and make it void since its
return value is not really used for anything else than setting the default
dram_size.
> - }
>
> ret = amd_pmc_send_cmd(dev, S2D_DRAM_SIZE, &dev->dram_size, dev->s2d_msg_id, true);
> if (ret || !dev->dram_size)
>
--
i.
next prev parent reply other threads:[~2023-11-13 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 6:17 [PATCH v2] platform/x86/amd/pmc: adjust amd_pmc_get_dram_size() behavior Shyam Sundar S K
2023-11-09 14:15 ` Mario Limonciello
2023-11-13 13:10 ` Ilpo Järvinen [this message]
2023-11-13 18:57 ` Mark Hasemeyer
2023-11-16 7:29 ` Shyam Sundar S K
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=a7435bf5-4465-5835-9595-ab453c8f125c@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Sanket.Goswami@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=hdegoede@redhat.com \
--cc=mario.limonciello@amd.com \
--cc=markgross@kernel.org \
--cc=markhas@chromium.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