From: Mario Limonciello <mario.limonciello@amd.com>
To: Rong Zhang <i@rong.moe>, Clemens Ladisch <clemens@ladisch.de>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
"Borislav Petkov (AMD)" <bp@alien8.de>
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (k10temp) Add device ID for Strix Halo
Date: Mon, 25 Aug 2025 15:43:18 -0500 [thread overview]
Message-ID: <9843500a-9e7e-4d5b-a06b-5fe012aed22c@amd.com> (raw)
In-Reply-To: <20250823180443.85512-1-i@rong.moe>
On 8/23/2025 1:04 PM, Rong Zhang wrote:
> The device ID of Strix Halo Data Fabric Function 3 has been in the tree
> since commit 0e640f0a47d8 ("x86/amd_nb: Add new PCI IDs for AMD family
> 0x1a"), but is somehow missing from k10temp_id_table.
>
> Add it so that it works out of the box.
>
> Tested on Beelink GTR9 Pro Mini PC.
>
> Signed-off-by: Rong Zhang <i@rong.moe>
Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
> drivers/hwmon/k10temp.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/hwmon/k10temp.c b/drivers/hwmon/k10temp.c
> index 2f90a2e9ad49..b98d5ec72c4f 100644
> --- a/drivers/hwmon/k10temp.c
> +++ b/drivers/hwmon/k10temp.c
> @@ -565,6 +565,7 @@ static const struct pci_device_id k10temp_id_table[] = {
> { PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_1AH_M20H_DF_F3) },
> { PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_1AH_M50H_DF_F3) },
> { PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_1AH_M60H_DF_F3) },
> + { PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_1AH_M70H_DF_F3) },
> { PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_1AH_M90H_DF_F3) },
> { PCI_VDEVICE(HYGON, PCI_DEVICE_ID_AMD_17H_DF_F3) },
> {}
>
> base-commit: 9703c672af8dd3573c76ce509dfff26bf6c4768d
next prev parent reply other threads:[~2025-08-25 20:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-23 18:04 [PATCH] hwmon: (k10temp) Add device ID for Strix Halo Rong Zhang
2025-08-25 20:43 ` Mario Limonciello [this message]
2025-08-27 15:55 ` Guenter Roeck
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=9843500a-9e7e-4d5b-a06b-5fe012aed22c@amd.com \
--to=mario.limonciello@amd.com \
--cc=bp@alien8.de \
--cc=clemens@ladisch.de \
--cc=i@rong.moe \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.