From: Julia Filipchuk <julia.filipchuk@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
Julia Filipchuk <julia.filipchuk@intel.com>,
John Harrison <John.C.Harrison@Intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [PATCH 5/7] drm/xe/pvc: Add GuC firmware definition
Date: Mon, 12 Jan 2026 10:07:40 -0800 [thread overview]
Message-ID: <20260112180809.1474677-14-julia.filipchuk@intel.com> (raw)
In-Reply-To: <20260112180809.1474677-9-julia.filipchuk@intel.com>
From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Add pre-release support for PVC.
UAPI version 1.13.4.
Signed-off-by: Julia Filipchuk <julia.filipchuk@intel.com>
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20250403185619.1555853-7-John.C.Harrison@Intel.com
Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Signed-off-by: Julia Filipchuk <julia.filipchuk@intel.com>
---
drivers/gpu/drm/xe/xe_uc_fw.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/xe/xe_uc_fw.c b/drivers/gpu/drm/xe/xe_uc_fw.c
index 3bff84ab4b5d..48305b5178c7 100644
--- a/drivers/gpu/drm/xe/xe_uc_fw.c
+++ b/drivers/gpu/drm/xe/xe_uc_fw.c
@@ -119,6 +119,7 @@ struct fw_blobs_by_type {
fw_def(BATTLEMAGE, GT_TYPE_ANY, major_ver(xe, guc, bmg, 70, 55, 3)) \
fw_def(LUNARLAKE, GT_TYPE_ANY, major_ver(xe, guc, lnl, 70, 53, 0)) \
fw_def(METEORLAKE, GT_TYPE_ANY, major_ver(i915, guc, mtl, 70, 53, 0)) \
+ fw_def(PVC, GT_TYPE_ANY, mmp_ver(xe, guc, pvc, 70, 44, 1)) \
fw_def(DG2, GT_TYPE_ANY, major_ver(i915, guc, dg2, 70, 53, 0)) \
fw_def(DG1, GT_TYPE_ANY, major_ver(i915, guc, dg1, 70, 44, 1)) \
fw_def(ALDERLAKE_N, GT_TYPE_ANY, major_ver(i915, guc, tgl, 70, 44, 1)) \
--
2.51.0
next prev parent reply other threads:[~2026-01-12 18:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 18:07 [PATCH 0/7] drm/xe/guc: Recommend GuC v70.55.3 for BMG, PTL Julia Filipchuk
2026-01-12 18:07 ` [PATCH 1/7] Revert "topic/for-xe-CI: drm/xe/cri: Define GuC firmware for CRI" Julia Filipchuk
2026-01-12 18:07 ` [PATCH 2/7] Revert "drm/xe/nvls: Define GuC firmware for NVL-S" Julia Filipchuk
2026-01-12 18:07 ` [PATCH 3/7] Revert "drm/xe/pvc: Add GuC firmware definition" Julia Filipchuk
2026-01-12 18:07 ` [PATCH 4/7] drm/xe/guc: Recommend GuC v70.55.3 for BMG,PTL Julia Filipchuk
2026-01-14 23:56 ` Daniele Ceraolo Spurio
2026-01-12 18:07 ` Julia Filipchuk [this message]
2026-01-12 18:07 ` [PATCH 6/7] drm/xe/nvls: Define GuC firmware for NVL-S Julia Filipchuk
2026-01-12 18:07 ` [PATCH 7/7] topic/for-xe-CI: drm/xe/cri: Define GuC firmware for CRI Julia Filipchuk
2026-01-12 18:14 ` ✗ CI.checkpatch: warning for drm/xe/guc: Recommend GuC v70.55.3 for BMG, PTL Patchwork
2026-01-12 18:15 ` ✓ CI.KUnit: success " Patchwork
2026-01-12 18:58 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-12 23:07 ` ✗ Xe.CI.Full: failure " Patchwork
2026-01-13 16:42 ` Julia Filipchuk
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=20260112180809.1474677-14-julia.filipchuk@intel.com \
--to=julia.filipchuk@intel.com \
--cc=John.C.Harrison@Intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@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