From: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Sanket.Goswami@amd.com, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v5 00/10] platform/x86/amd/pmc: Updates to AMD PMC driver
Date: Tue, 3 Dec 2024 10:41:58 +0530 [thread overview]
Message-ID: <da755bfb-3b29-4b4c-adf4-7ce800f771c9@amd.com> (raw)
In-Reply-To: <abf2b911-e3a1-f8fb-5edf-82cf989fc4ec@linux.intel.com>
On 12/2/2024 23:23, Ilpo Järvinen wrote:
> On Fri, 8 Nov 2024, Shyam Sundar S K wrote:
>
>> Updates include:
>> - Rework STB code and move into a separate file
>> - Update the code with new IP block information for newer SoCs
>> - Add STB support for new generation
>> - Add STB support for Ryzen desktop variants
>> - Updates to MAINTAINERS record.
>>
>> v5:
>> ----
>> - Merge patch1 and 2 of v4
>> - Update Ilpo tags
>> - drop explicit typecasting.
>> - Use switch() for getting the message port
>> - Rename function names
>
> Thanks for the update. I applied v5 to review-ilpo-next branch. I ended up
> reordering ips_ptr and active_ips members in the struct amd_pmc_dev to
> group them together.
>
> While checking this series out, I notice there's also one sparse warning
> in amd/pmc dir:
>
> drivers/platform/x86/amd/pmc/mp2_stb.c:105:30: warning: incorrect type in
> assignment (different address spaces)
> drivers/platform/x86/amd/pmc/mp2_stb.c:105:30: expected void [noderef]
> __iomem *vslbase
> drivers/platform/x86/amd/pmc/mp2_stb.c:105:30: got void *
>
> If you could fix that please.
>
Thank you, Ilpo. Sure, I will send out a fix in a while.
Thanks,
Shyam
prev parent reply other threads:[~2024-12-03 5:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 7:08 [PATCH v5 00/10] platform/x86/amd/pmc: Updates to AMD PMC driver Shyam Sundar S K
2024-11-08 7:08 ` [PATCH v5 01/10] platform/x86/amd/pmc: Move STB block into amd_pmc_s2d_init() Shyam Sundar S K
2024-11-08 7:08 ` [PATCH v5 02/10] platform/x86/amd/pmc: Move STB functionality to a new file for better code organization Shyam Sundar S K
2024-11-08 7:08 ` [PATCH v5 03/10] platform/x86/amd/pmc: Update function names to align with new STB file Shyam Sundar S K
2024-11-08 7:08 ` [PATCH v5 04/10] platform/x86/amd/pmc: Define enum for S2D/PMC msg_port and add helper function Shyam Sundar S K
2024-11-08 7:08 ` [PATCH v5 05/10] platform/x86/amd/pmc: Isolate STB code changes to a new file Shyam Sundar S K
2024-11-08 7:08 ` [PATCH v5 06/10] platform/x86/amd/pmc: Use ARRAY_SIZE() to fill num_ips information Shyam Sundar S K
2024-11-08 7:08 ` [PATCH v5 07/10] platform/x86/amd/pmc: Update IP information structure for newer SoCs Shyam Sundar S K
2024-11-08 7:08 ` [PATCH v5 08/10] platform/x86/amd/pmc: Update S2D message id for 1Ah Family 70h model Shyam Sundar S K
2024-11-08 7:08 ` [PATCH v5 09/10] platform/x86/amd/pmc: Add STB support for AMD Desktop variants Shyam Sundar S K
2024-11-08 7:08 ` [PATCH v5 10/10] MAINTAINERS: Change AMD PMC driver status to "Supported" Shyam Sundar S K
2024-11-08 7:13 ` [PATCH v5 00/10] platform/x86/amd/pmc: Updates to AMD PMC driver Shyam Sundar S K
2024-12-02 17:53 ` Ilpo Järvinen
2024-12-03 5:11 ` Shyam Sundar S K [this message]
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=da755bfb-3b29-4b4c-adf4-7ce800f771c9@amd.com \
--to=shyam-sundar.s-k@amd.com \
--cc=Sanket.Goswami@amd.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.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