Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julia Filipchuk <julia.filipchuk@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Matt Roper <matthew.d.roper@intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [PATCH topic/xe-for-CI 3/4] drm/xe/nvls: Define GuC firmware for NVL-S
Date: Tue,  6 Jan 2026 13:27:06 -0800	[thread overview]
Message-ID: <20260106212758.1172984-9-julia.filipchuk@intel.com> (raw)
In-Reply-To: <20260106212758.1172984-6-julia.filipchuk@intel.com>

From: Matt Roper <matthew.d.roper@intel.com>

Although NVL-S has a similar Xe3 to PTL/WCL, it requires a unique GuC
firmware.

Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
Link: https://lore.kernel.org/r/20251016-xe3p-v3-12-3dd173a3097a@intel.com
Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
Signed-off-by: Rodrigo Vivi <rodrigo.vivi@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 cacbf89e8f68..2980d0b99e95 100644
--- a/drivers/gpu/drm/xe/xe_uc_fw.c
+++ b/drivers/gpu/drm/xe/xe_uc_fw.c
@@ -115,6 +115,7 @@ struct fw_blobs_by_type {
 #define XE_GT_TYPE_ANY XE_GT_TYPE_UNINITIALIZED
 
 #define XE_GUC_FIRMWARE_DEFS(fw_def, mmp_ver, major_ver)					\
+	fw_def(NOVALAKE_S,	GT_TYPE_ANY,	mmp_ver(xe,	guc,	nvl,	70, 55, 4))	\
 	fw_def(PANTHERLAKE,	GT_TYPE_ANY,	major_ver(xe,	guc,	ptl,	70, 54, 0))	\
 	fw_def(BATTLEMAGE,	GT_TYPE_ANY,	major_ver(xe,	guc,	bmg,	70, 54, 0))	\
 	fw_def(LUNARLAKE,	GT_TYPE_ANY,	major_ver(xe,	guc,	lnl,	70, 53, 0))	\
-- 
2.51.0


  parent reply	other threads:[~2026-01-06 21:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06 21:27 [PATCH topic/xe-for-CI 0/4] drm/xe/guc: Bump GUC version for NVL-S, CRI Julia Filipchuk
2026-01-06 21:27 ` [PATCH topic/xe-for-CI 1/4] Revert "topic/for-xe-CI: drm/xe/cri: Define GuC firmware for CRI" Julia Filipchuk
2026-01-06 21:27 ` [PATCH topic/xe-for-CI 2/4] Revert "drm/xe/nvls: Define GuC firmware for NVL-S" Julia Filipchuk
2026-01-06 21:27 ` Julia Filipchuk [this message]
2026-01-06 21:27 ` [PATCH topic/xe-for-CI 4/4] topic/for-xe-CI: drm/xe/cri: Define GuC firmware for CRI Julia Filipchuk
2026-01-06 21:51 ` ✗ CI.checkpatch: warning for drm/xe/guc: Bump GUC version for NVL-S, CRI Patchwork
2026-01-08 19:01   ` Julia Filipchuk
2026-01-06 21:53 ` ✓ CI.KUnit: success " Patchwork
2026-01-06 22:29 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-07  1:21 ` ✗ Xe.CI.Full: failure " Patchwork
2026-01-08 19:00   ` 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=20260106212758.1172984-9-julia.filipchuk@intel.com \
    --to=julia.filipchuk@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.d.roper@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