From: Matt Roper <matthew.d.roper@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: matthew.d.roper@intel.com
Subject: [PATCH] drm/xe/bmg: Add one additional PCI ID
Date: Tue, 25 Mar 2025 15:47:10 -0700 [thread overview]
Message-ID: <20250325224709.4073080-2-matthew.d.roper@intel.com> (raw)
One additional BMG PCI ID has been added to the spec; make sure our
driver recognizes devices with this ID properly.
Bspec: 68090
Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
---
include/drm/intel/pciids.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/drm/intel/pciids.h b/include/drm/intel/pciids.h
index 4736ea525048..d212848d07f3 100644
--- a/include/drm/intel/pciids.h
+++ b/include/drm/intel/pciids.h
@@ -850,6 +850,7 @@
MACRO__(0xE20C, ## __VA_ARGS__), \
MACRO__(0xE20D, ## __VA_ARGS__), \
MACRO__(0xE210, ## __VA_ARGS__), \
+ MACRO__(0xE211, ## __VA_ARGS__), \
MACRO__(0xE212, ## __VA_ARGS__), \
MACRO__(0xE215, ## __VA_ARGS__), \
MACRO__(0xE216, ## __VA_ARGS__)
--
2.48.1
next reply other threads:[~2025-03-25 22:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 22:47 Matt Roper [this message]
2025-03-25 23:25 ` [PATCH] drm/xe/bmg: Add one additional PCI ID Taylor, Clinton A
2025-03-26 1:15 ` ✓ CI.Patch_applied: success for " Patchwork
2025-03-26 1:16 ` ✓ CI.checkpatch: " Patchwork
2025-03-26 1:17 ` ✓ CI.KUnit: " Patchwork
2025-03-26 1:33 ` ✓ CI.Build: " Patchwork
2025-03-26 1:36 ` ✓ CI.Hooks: " Patchwork
2025-03-26 1:37 ` ✓ CI.checksparse: " Patchwork
2025-03-26 2:16 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-03-26 20:39 ` Matt Roper
2025-03-26 4:30 ` [PATCH] " Lucas De Marchi
2025-03-26 14:09 ` ✗ Xe.CI.Full: failure for " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2025-07-04 10:35 [PATCH] " Ravi Kumar Vodapalli
2025-07-04 10:48 ` Shekhar Chauhan
2025-07-04 12:04 ` Matthew Auld
2025-07-04 13:16 ` Vodapalli, Ravi Kumar
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=20250325224709.4073080-2-matthew.d.roper@intel.com \
--to=matthew.d.roper@intel.com \
--cc=intel-xe@lists.freedesktop.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