From: Bjorn Helgaas <helgaas@kernel.org>
To: Lin Wang <wanglin@open-hieco.net>
Cc: Borislav Petkov <bp@alien8.de>,
yazen.ghannam@amd.com, mario.limonciello@amd.com,
tglx@linutronix.de, mingo@redhat.com,
dave.hansen@linux.intel.com, "H. Peter Anvin" <hpa@zytor.com>,
bhelgaas@google.com, x86@kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/5] pci_ids: Add Hygon Family 0x18 DF F3/F4 device IDs
Date: Thu, 3 Sep 2026 17:10:43 -0500 [thread overview]
Message-ID: <20260903221043.GA2261875@bhelgaas> (raw)
In-Reply-To: <20260901071700.3255382-2-wanglin@open-hieco.net>
On Tue, Sep 01, 2026 at 03:16:56PM +0800, Lin Wang wrote:
> Hygon Family 0x18 node discovery identifies Data Fabric misc (F3) and
> link (F4) functions by PCI ID rather than a fixed PCI slot.
>
> Models 0x04 use 0x1463/0x1464, with 0x1493/0x1494 on the mixed-silicon
> variant. Models 0x05 through 0x08 use 0x14b3/0x14b4.
>
> Some IDs have the same numeric values as AMD DF devices. PCI identity
> also includes the vendor, so Hygon-prefixed names keep the two vendors'
> definitions independent.
>
> Signed-off-by: Lin Wang <wanglin@open-hieco.net>
> ---
> include/linux/pci_ids.h | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
> index 63774ae2bf71..d9f3e01033f9 100644
> --- a/include/linux/pci_ids.h
> +++ b/include/linux/pci_ids.h
> @@ -2615,6 +2615,12 @@
> #define PCI_VENDOR_ID_ROCKCHIP 0x1d87
>
> #define PCI_VENDOR_ID_HYGON 0x1d94
> +#define PCI_DEVICE_ID_HYGON_18H_M04H_DF_F3 0x1463
> +#define PCI_DEVICE_ID_HYGON_18H_M04H_DF_F4 0x1464
> +#define PCI_DEVICE_ID_HYGON_18H_M04H_DF_F3B 0x1493
> +#define PCI_DEVICE_ID_HYGON_18H_M04H_DF_F4B 0x1494
> +#define PCI_DEVICE_ID_HYGON_18H_M05H_DF_F3 0x14b3
> +#define PCI_DEVICE_ID_HYGON_18H_M05H_DF_F4 0x14b4
It looks like these are only needed in one place, so per the note:
* Do not add new entries to this file unless the definitions
* are shared between multiple drivers.
the #defines should probably be added in the
arch/x86/kernel/hygon_node.c (or just use the raw hex values).
This helps reduce conflicts when backporting changes like this.
next prev parent reply other threads:[~2026-09-03 22:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 7:16 [PATCH v4 0/5] x86/hygon: Add Family 0x18 DF node enumeration and SMN access Lin Wang
2026-09-01 7:16 ` [PATCH v4 1/5] pci_ids: Add Hygon Family 0x18 DF F3/F4 device IDs Lin Wang
2026-09-03 22:10 ` Bjorn Helgaas [this message]
2026-09-04 3:18 ` Lin Wang
2026-09-01 7:16 ` [PATCH v4 2/5] x86/hygon: Add Family 0x18 DF node enumeration Lin Wang
2026-09-01 7:16 ` [PATCH v4 3/5] x86/hygon: Map CPU NodeIds to DF nodes Lin Wang
2026-09-01 7:16 ` [PATCH v4 4/5] x86/amd_node: Skip SMN setup on Hygon Fam18h models 0x04-0x08 Lin Wang
2026-09-02 2:48 ` Borislav Petkov
2026-09-02 6:22 ` Lin Wang
2026-09-02 15:13 ` Borislav Petkov
2026-09-03 1:49 ` Lin Wang
2026-09-03 17:34 ` Yazen Ghannam
2026-09-04 2:43 ` Lin Wang
2026-09-04 5:36 ` Borislav Petkov
2026-09-04 6:26 ` Lin Wang
2026-09-01 7:17 ` [PATCH v4 5/5] x86/hygon: Add Family 0x18 SMN access Lin Wang
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=20260903221043.GA2261875@bhelgaas \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=wanglin@open-hieco.net \
--cc=x86@kernel.org \
--cc=yazen.ghannam@amd.com \
/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
all inboxes | Powered by JetHome®