Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John.C.Harrison@Intel.com
To: Intel-Xe@Lists.FreeDesktop.Org
Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
	Matt Atwood <matthew.s.atwood@intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: [PATCH 8/8] drm/xe/ptl: Define HuC FW version for PTL
Date: Thu,  3 Apr 2025 11:56:18 -0700	[thread overview]
Message-ID: <20250403185619.1555853-9-John.C.Harrison@Intel.com> (raw)
In-Reply-To: <20250403185619.1555853-1-John.C.Harrison@Intel.com>

From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>

First HuC release for PTL. Note that the HuC team now only releases
GSC-enabled blobs, so we don't need the "_gsc" postfix to identify
the variant anymore. The driver can identify the type of binary at
runtime no matter the name.

Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Signed-off-by: Matt Atwood <matthew.s.atwood@intel.com>
Acked-by: Lucas De Marchi <lucas.demarchi@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20241011163612.6558-1-matthew.s.atwood@intel.com
Signed-off-by: Lucas De Marchi <lucas.demarchi@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 1db598d3b1de..40d48da19243 100644
--- a/drivers/gpu/drm/xe/xe_uc_fw.c
+++ b/drivers/gpu/drm/xe/xe_uc_fw.c
@@ -128,6 +128,7 @@ struct fw_blobs_by_type {
 	fw_def(TIGERLAKE,	GT_TYPE_ANY,	major_ver(i915,	guc,	tgl,	70, 44, 1))
 
 #define XE_HUC_FIRMWARE_DEFS(fw_def, mmp_ver, no_ver)		\
+	fw_def(PANTHERLAKE,	GT_TYPE_ANY,	mmp_ver(xe,	huc,		ptl, 10, 2, 1))	\
 	fw_def(BATTLEMAGE,	GT_TYPE_ANY,	no_ver(xe,	huc,		bmg))		\
 	fw_def(LUNARLAKE,	GT_TYPE_ANY,	no_ver(xe,	huc,		lnl))		\
 	fw_def(METEORLAKE,	GT_TYPE_ANY,	no_ver(i915,	huc_gsc,	mtl))		\
-- 
2.49.0


  parent reply	other threads:[~2025-04-03 18:56 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-03 18:56 [PATCH 0/8] Enable w/a 16026508708 John.C.Harrison
2025-04-03 18:56 ` [PATCH 1/8] drm/xe/guc: " John.C.Harrison
2025-04-08 22:08   ` Daniele Ceraolo Spurio
2025-04-03 18:56 ` [PATCH 2/8] Revert "drm/xe/ptl: Define HuC FW version for PTL" John.C.Harrison
2025-04-03 18:56 ` [PATCH 3/8] Revert "drm/xe/ptl: Add GuC firmware definition" John.C.Harrison
2025-04-03 18:56 ` [PATCH 4/8] Revert "drm/xe/pvc: " John.C.Harrison
2025-04-03 18:56 ` [PATCH 5/8] drm/xe/guc: Bump the recommended GuC version to 70.44.1 John.C.Harrison
2025-04-08 22:15   ` Daniele Ceraolo Spurio
2025-04-08 23:54     ` John Harrison
2025-04-10 19:22       ` Daniele Ceraolo Spurio
2025-04-03 18:56 ` [PATCH 6/8] drm/xe/pvc: Add GuC firmware definition John.C.Harrison
2025-04-03 18:56 ` [PATCH 7/8] drm/xe/ptl: " John.C.Harrison
2025-04-03 18:56 ` John.C.Harrison [this message]
2025-04-04  1:34 ` ✓ CI.Patch_applied: success for Enable w/a 16026508708 Patchwork
2025-04-04  1:34 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-04  1:35 ` ✓ CI.KUnit: success " Patchwork
2025-04-04  1:52 ` ✓ CI.Build: " Patchwork
2025-04-04  1:54 ` ✓ CI.Hooks: " Patchwork
2025-04-04  1:56 ` ✓ CI.checksparse: " Patchwork
2025-04-04  2:14 ` ✓ Xe.CI.BAT: " Patchwork
2025-04-04 11:07 ` ✗ Xe.CI.Full: failure " Patchwork
2025-04-08 19:35 ` ✓ CI.Patch_applied: success for Enable w/a 16026508708 (rev2) Patchwork
2025-04-08 19:35 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-08 19:36 ` ✓ CI.KUnit: success " Patchwork
2025-04-08 19:52 ` ✓ CI.Build: " Patchwork
2025-04-08 19:55 ` ✓ CI.Hooks: " Patchwork
2025-04-08 19:56 ` ✓ CI.checksparse: " Patchwork
2025-04-08 20:18 ` ✓ Xe.CI.BAT: " Patchwork
2025-04-08 21:52 ` ✗ Xe.CI.Full: failure " Patchwork
2025-04-10 21:25 ` [PATCH 0/8] Enable w/a 16026508708 Lucas De Marchi

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=20250403185619.1555853-9-John.C.Harrison@Intel.com \
    --to=john.c.harrison@intel.com \
    --cc=Intel-Xe@Lists.FreeDesktop.Org \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=lucas.demarchi@intel.com \
    --cc=matthew.s.atwood@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