From: himanshu.girotra@intel.com
To: ramadevi.gandi@intel.com, nishit.sharma@intel.com,
aditya.chauhan@intel.com, kamil.konieczny@intel.com,
shekhar.chauhan@intel.com, zbigniew.kempczynski@intel.com,
igt-dev@lists.freedesktop.org
Subject: [PATCH v3 i-g-t 1/4] lib/pciids: sync with kernel commit be07d8f707e4
Date: Thu, 12 Mar 2026 21:33:25 +0530 [thread overview]
Message-ID: <20260312160328.9462-2-himanshu.girotra@intel.com> (raw)
In-Reply-To: <20260312160328.9462-1-himanshu.girotra@intel.com>
From: Himanshu Girotra <himanshu.girotra@intel.com>
Synchronize PCI IDs with drm-next kernel up to be07d8f707e4,
which includes the following changes:
commit be07d8f707e4 ("drm/xe/nvlp: Add NVL-P platform definition")
commit 32620e176443 ("drm/pcids: Split PTL pciids group to make wcl subplatform")
commit aaecfadc22cc ("drm/intel/bmg: Allow device ID usage with single-argument macros")
Signed-off-by: Himanshu Girotra <himanshu.girotra@intel.com>
Reviewed-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
---
lib/pciids.h | 19 +++++++++++++++++--
1 file changed, 17 insertions(+), 2 deletions(-)
diff --git a/lib/pciids.h b/lib/pciids.h
index 6e53fb4cd..33b91cb2e 100644
--- a/lib/pciids.h
+++ b/lib/pciids.h
@@ -861,7 +861,7 @@
MACRO__(0xE216, ## __VA_ARGS__)
#define INTEL_BMG_IDS(MACRO__, ...) \
- INTEL_BMG_G21_IDS(MACRO__, __VA_ARGS__), \
+ INTEL_BMG_G21_IDS(MACRO__, ## __VA_ARGS__), \
MACRO__(0xE220, ## __VA_ARGS__), \
MACRO__(0xE221, ## __VA_ARGS__), \
MACRO__(0xE222, ## __VA_ARGS__), \
@@ -880,7 +880,10 @@
MACRO__(0xB08F, ## __VA_ARGS__), \
MACRO__(0xB090, ## __VA_ARGS__), \
MACRO__(0xB0A0, ## __VA_ARGS__), \
- MACRO__(0xB0B0, ## __VA_ARGS__), \
+ MACRO__(0xB0B0, ## __VA_ARGS__)
+
+/* WCL */
+#define INTEL_WCL_IDS(MACRO__, ...) \
MACRO__(0xFD80, ## __VA_ARGS__), \
MACRO__(0xFD81, ## __VA_ARGS__)
@@ -897,4 +900,16 @@
#define INTEL_CRI_IDS(MACRO__, ...) \
MACRO__(0x674C, ## __VA_ARGS__)
+/* NVL-P */
+#define INTEL_NVLP_IDS(MACRO__, ...) \
+ MACRO__(0xD750, ## __VA_ARGS__), \
+ MACRO__(0xD751, ## __VA_ARGS__), \
+ MACRO__(0xD752, ## __VA_ARGS__), \
+ MACRO__(0xD753, ## __VA_ARGS__), \
+ MACRO__(0XD754, ## __VA_ARGS__), \
+ MACRO__(0XD755, ## __VA_ARGS__), \
+ MACRO__(0XD756, ## __VA_ARGS__), \
+ MACRO__(0XD757, ## __VA_ARGS__), \
+ MACRO__(0xD75F, ## __VA_ARGS__)
+
#endif /* __PCIIDS_H__ */
--
2.50.1
next prev parent reply other threads:[~2026-03-12 16:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 16:03 [PATCH v3 i-g-t 0/4] lib: Add NVL-P and WCL support himanshu.girotra
2026-03-12 16:03 ` himanshu.girotra [this message]
2026-03-12 16:03 ` [PATCH v3 i-g-t 2/4] lib: Add NVL-P support himanshu.girotra
2026-03-12 16:03 ` [PATCH v3 i-g-t 3/4] lib: Add WildcatLake support himanshu.girotra
2026-03-12 16:03 ` [PATCH v3 i-g-t 4/4] lib: Add WildcatLake to compute kernel tables himanshu.girotra
2026-03-13 5:21 ` Dandamudi, Priyanka
2026-03-12 21:46 ` ✓ Xe.CI.BAT: success for lib: Add NVL-P and WCL support (rev3) Patchwork
2026-03-12 22:00 ` ✓ i915.CI.BAT: " Patchwork
2026-03-14 0:29 ` ✓ Xe.CI.FULL: " Patchwork
2026-03-14 0:33 ` ✗ i915.CI.Full: failure " Patchwork
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=20260312160328.9462-2-himanshu.girotra@intel.com \
--to=himanshu.girotra@intel.com \
--cc=aditya.chauhan@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@intel.com \
--cc=nishit.sharma@intel.com \
--cc=ramadevi.gandi@intel.com \
--cc=shekhar.chauhan@intel.com \
--cc=zbigniew.kempczynski@intel.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