From: Mario Limonciello <mario.limonciello@amd.com>
To: "Mark Hasemeyer" <markhas@chromium.org>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
Mark Gross <markgross@kernel.org>,
Sanket Goswami <Sanket.Goswami@amd.com>,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v1] platform/x86/amd/pmc: Get smu version before reading dram size
Date: Mon, 30 Oct 2023 11:17:52 -0500 [thread overview]
Message-ID: <bd018335-3b2c-4233-aae3-407e239fd393@amd.com> (raw)
In-Reply-To: <CANg-bXCcNPjmQC9vgd1JJcV4QoruhhbeEg8o=S9K-22kb746kQ@mail.gmail.com>
On 10/30/2023 11:09, Mark Hasemeyer wrote:
>> Hi,
>>
>> Thank you for your patch. This has already come up but no acceptable patch
>> has emerged since. Please see this thread for what needs to be done if you
>> want to provide one (or maybe Shyam already has one which has just not
>> been sent out yet):
>>
>> https://lore.kernel.org/platform-driver-x86/3b224c62-a1d8-41bd-aced-5825f5f20e66@amd.com/
>>
>> (Since this dram size is on an init path that always needs SMU version,
>> the SMU version can just be called by the init unconditonally rather than
>> adding more of this lazy initialization everywhere).
>
> Thanks for pointing me to that thread. I think Shyam/AMD can come up
> with a better long term solution, but it may be worth pushing this
> patch through for a couple reasons:
> 1. Probing of the driver currently fails on STB enabled systems with a
> Mendocino SoC. A slower boot time is better than the driver failing to
> load IMO.
> 2. This patch only affects Mendocino SoCs, and was a suggested
> solution from Mario in the thread you mentioned.
>
> That said, I can also just disable STB for now...
It's debugfs. The vast majority of people won't need to access it even
if STB is turned on by default. It should only really be needed in
error cases.
So how about if the STB init is pushed into the lazy init path as well?
You can make the files at probe, and then check in their first access if
init was done.
next prev parent reply other threads:[~2023-10-30 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 21:28 [PATCH v1] platform/x86/amd/pmc: Get smu version before reading dram size Mark Hasemeyer
2023-10-30 9:24 ` Ilpo Järvinen
2023-10-30 16:09 ` Mark Hasemeyer
2023-10-30 16:17 ` Mario Limonciello [this message]
2023-10-31 7:53 ` Shyam Sundar S K
2023-10-31 15:17 ` Mark Hasemeyer
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=bd018335-3b2c-4233-aae3-407e239fd393@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=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=markhas@chromium.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=stable@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