From: Mario Limonciello <mario.limonciello@amd.com>
To: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
hdegoede@redhat.com, ilpo.jarvinen@linux.intel.com,
markgross@kernel.org
Cc: Sanket.Goswami@amd.com, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH 1/2] platform/x86/amd/pmc: Fix fetching DRAM size mechanism
Date: Mon, 9 Oct 2023 09:55:12 -0500 [thread overview]
Message-ID: <3e42aa76-64c5-4276-a496-433d788e0779@amd.com> (raw)
In-Reply-To: <20231009144748.24054-1-Shyam-sundar.S-k@amd.com>
On 10/9/2023 09:47, Shyam Sundar S K wrote:
> amd_pmc_get_dram_size() is used to get the DRAM size information. But in
> the current code, mailbox command to get the DRAM size info is sent based
> on the values of dev->major and dev->minor.
>
> But dev->major and dev->minor will have either junk or zero assigned to
> them until at least once a call to amd_pmc_get_smu_version() is made which
> ideally populates dev->major and dev->minor.
>
> Add a missing amd_pmc_get_smu_version() call to amd_pmc_get_dram_size().
>
> 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>
> ---
> based on review-ilpo, can be added on top of recent stb changes
Hmm, so this is actually going to mean that we end up with a round trip
call to the SMU as part of probe to get the version when STB is initialized.
I think that's going to translate to a longer amd_pmc startup time,
which could be problematic if a platform leaves STB enabled by default.
At a minimum I would suggest to only do the version check when it's one
that needs it (IE AMD_CPU_ID_YC right now). But otherwise this s2d
initialization can't happen the first time it's used?
>
> drivers/platform/x86/amd/pmc/pmc.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/platform/x86/amd/pmc/pmc.c b/drivers/platform/x86/amd/pmc/pmc.c
> index 1424c03c1f03..92adf4523736 100644
> --- a/drivers/platform/x86/amd/pmc/pmc.c
> +++ b/drivers/platform/x86/amd/pmc/pmc.c
> @@ -981,6 +981,10 @@ static int amd_pmc_get_dram_size(struct amd_pmc_dev *dev)
> {
> int ret;
>
> + ret = amd_pmc_get_smu_version(dev);
> + if (ret)
> + return ret;
> +
> switch (dev->cpu_id) {
> case AMD_CPU_ID_YC:
> if (!(dev->major > 90 || (dev->major == 90 && dev->minor > 39))) {
next prev parent reply other threads:[~2023-10-09 14:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 14:47 [PATCH 1/2] platform/x86/amd/pmc: Fix fetching DRAM size mechanism Shyam Sundar S K
2023-10-09 14:47 ` [PATCH 2/2] platform/x86/amd/pmc: Move structures to pmc header Shyam Sundar S K
2023-10-09 14:56 ` Mario Limonciello
2023-10-09 15:39 ` Ilpo Järvinen
2023-10-09 15:47 ` Shyam Sundar S K
2023-10-09 15:49 ` Ilpo Järvinen
2023-10-09 14:55 ` Mario Limonciello [this message]
2023-10-09 15:39 ` [PATCH 1/2] platform/x86/amd/pmc: Fix fetching DRAM size mechanism Shyam Sundar S K
2023-10-09 15:42 ` Mario Limonciello
2023-10-09 14:59 ` Ilpo Järvinen
2023-10-09 15:42 ` 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=3e42aa76-64c5-4276-a496-433d788e0779@amd.com \
--to=mario.limonciello@amd.com \
--cc=Sanket.Goswami@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=markgross@kernel.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