Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Shekhar Chauhan <shekhar.chauhan@intel.com>,
	James Ausmus <james.ausmus@intel.com>,
	Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>,
	Tejas Upadhyay <tejas.upadhyay@intel.com>,
	Matt Roper <matthew.d.roper@intel.com>
Subject: [PATCH 3/3] drm/xe/xe2_hpg: Define additional Xe2_HPG GMD_ID
Date: Wed,  4 Jun 2025 20:22:36 +0530	[thread overview]
Message-ID: <20250604145236.1143122-4-dnyaneshwar.bhadane@intel.com> (raw)
In-Reply-To: <20250604145236.1143122-1-dnyaneshwar.bhadane@intel.com>

From: Shekhar Chauhan <shekhar.chauhan@intel.com>

Add another GMD_ID for Xe2_HPG

Signed-off-by: Shekhar Chauhan <shekhar.chauhan@intel.com>
Signed-off-by: James Ausmus <james.ausmus@intel.com>
Signed-off-by: Dnyaneshwar Bhadane <dnyaneshwar.bhadane@intel.com>
Reviewed-by: Tejas Upadhyay <tejas.upadhyay@intel.com>
Reviewed-by: Matt Roper <matthew.d.roper@intel.com>
---
 drivers/gpu/drm/xe/xe_pci.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/gpu/drm/xe/xe_pci.c b/drivers/gpu/drm/xe/xe_pci.c
index b68c90910d82..83f0a76a81a5 100644
--- a/drivers/gpu/drm/xe/xe_pci.c
+++ b/drivers/gpu/drm/xe/xe_pci.c
@@ -179,6 +179,7 @@ static const struct xe_ip graphics_ips[] = {
 	{ 1271, "Xe_LPG", &graphics_xelpg },
 	{ 1274, "Xe_LPG+", &graphics_xelpg },
 	{ 2001, "Xe2_HPG", &graphics_xe2 },
+	{ 2002, "Xe2_HPG", &graphics_xe2 },
 	{ 2004, "Xe2_LPG", &graphics_xe2 },
 	{ 3000, "Xe3_LPG", &graphics_xe2 },
 	{ 3001, "Xe3_LPG", &graphics_xe2 },
-- 
2.34.1


  parent reply	other threads:[~2025-06-04 14:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-04 14:52 [PATCH v2 0/3] drm/xe/bmg: Update PCI Id's and Workarounds Dnyaneshwar Bhadane
2025-06-04 14:52 ` [PATCH 1/3] drm/xe/xe2_hpg: Add PCI IDs for xe2_hpg Dnyaneshwar Bhadane
2025-06-04 14:52 ` [PATCH v2 2/3] drm/xe/xe2_hpg: Add set of workarounds Dnyaneshwar Bhadane
2025-06-04 18:54   ` Matt Roper
2025-06-05 15:45     ` Lucas De Marchi
2025-06-05 18:05       ` Bhadane, Dnyaneshwar
2025-06-05 18:03     ` Bhadane, Dnyaneshwar
2025-06-04 14:52 ` Dnyaneshwar Bhadane [this message]
2025-06-04 15:13 ` ✓ CI.Patch_applied: success for drm/xe/bmg: Update PCI Id's and Workarounds (rev3) Patchwork
2025-06-04 15:13 ` ✓ CI.checkpatch: " Patchwork
2025-06-04 15:14 ` ✓ CI.KUnit: " Patchwork
2025-06-04 15:26 ` ✓ CI.Build: " Patchwork
2025-06-04 15:28 ` ✓ CI.Hooks: " Patchwork
2025-06-04 15:30 ` ✓ CI.checksparse: " Patchwork
2025-06-04 16:34 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-06-05 11:20 ` ✗ Xe.CI.Full: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2025-06-05 19:08 [PATCH v3 0/3] drm/xe/bmg: Update PCI Id's and Workarounds Dnyaneshwar Bhadane
2025-06-05 19:08 ` [PATCH 3/3] drm/xe/xe2_hpg: Define additional Xe2_HPG GMD_ID Dnyaneshwar Bhadane
2025-05-29 12:05 [PATCH 0/3] drm/xe/bmg: Update PCI Id's and Workarounds Dnyaneshwar Bhadane
2025-05-29 12:05 ` [PATCH 3/3] drm/xe/xe2_hpg: Define additional Xe2_HPG GMD_ID Dnyaneshwar Bhadane
2025-05-29 13:12   ` Upadhyay, Tejas
2025-05-29 21:03   ` Matt Roper

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=20250604145236.1143122-4-dnyaneshwar.bhadane@intel.com \
    --to=dnyaneshwar.bhadane@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=james.ausmus@intel.com \
    --cc=matthew.d.roper@intel.com \
    --cc=shekhar.chauhan@intel.com \
    --cc=tejas.upadhyay@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