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: John Harrison <John.C.Harrison@Intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: [PATCH v2 4/6] drm/xe/guc: Update to GuC firmware 70.19.2
Date: Fri,  2 Feb 2024 12:00:15 -0800	[thread overview]
Message-ID: <20240202200017.2133438-5-John.C.Harrison@Intel.com> (raw)
In-Reply-To: <20240202200017.2133438-1-John.C.Harrison@Intel.com>

From: John Harrison <John.C.Harrison@Intel.com>

API compatibility version: 1.8.2

Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
---
 drivers/gpu/drm/xe/xe_uc_fw.c | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/drivers/gpu/drm/xe/xe_uc_fw.c b/drivers/gpu/drm/xe/xe_uc_fw.c
index d3f0fe2101a7..d896c98dd0bb 100644
--- a/drivers/gpu/drm/xe/xe_uc_fw.c
+++ b/drivers/gpu/drm/xe/xe_uc_fw.c
@@ -103,14 +103,14 @@ struct fw_blobs_by_type {
 };
 
 #define XE_GUC_FIRMWARE_DEFS(fw_def, mmp_ver, major_ver)			\
-	fw_def(METEORLAKE,	major_ver(i915,	guc,	mtl,	70, 7, 0))	\
-	fw_def(DG2,		major_ver(i915,	guc,	dg2,	70, 5, 0))	\
-	fw_def(DG1,		major_ver(i915,	guc,	dg1,	70, 5, 0))	\
-	fw_def(ALDERLAKE_N,	major_ver(i915,	guc,	tgl,	70, 5, 0))	\
-	fw_def(ALDERLAKE_P,	major_ver(i915,	guc,	adlp,	70, 5, 0))	\
-	fw_def(ALDERLAKE_S,	major_ver(i915,	guc,	tgl,	70, 5, 0))	\
-	fw_def(ROCKETLAKE,	major_ver(i915,	guc,	tgl,	70, 5, 0))	\
-	fw_def(TIGERLAKE,	major_ver(i915,	guc,	tgl,	70, 5, 0))
+	fw_def(METEORLAKE,	major_ver(i915,	guc,	mtl,	70, 19, 2))	\
+	fw_def(DG2,		major_ver(i915,	guc,	dg2,	70, 19, 2))	\
+	fw_def(DG1,		major_ver(i915,	guc,	dg1,	70, 19, 2))	\
+	fw_def(ALDERLAKE_N,	major_ver(i915,	guc,	tgl,	70, 19, 2))	\
+	fw_def(ALDERLAKE_P,	major_ver(i915,	guc,	adlp,	70, 19, 2))	\
+	fw_def(ALDERLAKE_S,	major_ver(i915,	guc,	tgl,	70, 19, 2))	\
+	fw_def(ROCKETLAKE,	major_ver(i915,	guc,	tgl,	70, 19, 2))	\
+	fw_def(TIGERLAKE,	major_ver(i915,	guc,	tgl,	70, 19, 2))
 
 #define XE_HUC_FIRMWARE_DEFS(fw_def, mmp_ver, no_ver)		\
 	fw_def(METEORLAKE,	no_ver(i915,	huc_gsc,	mtl))		\
-- 
2.43.0


  parent reply	other threads:[~2024-02-02 20:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 20:00 [PATCH v2 0/6] Update to GuC 70.19.2 and add LNL John.C.Harrison
2024-02-02 20:00 ` [PATCH v2 1/6] Revert "drm/xe/guc: define LNL FW" John.C.Harrison
2024-02-02 20:00 ` [PATCH v2 2/6] Revert "drm/xe/guc: define PVC FW" John.C.Harrison
2024-02-02 20:00 ` [PATCH v2 3/6] drm/xe/uc: Include patch version in expectations John.C.Harrison
2024-02-02 20:00 ` John.C.Harrison [this message]
2024-02-02 20:00 ` [PATCH v2 5/6] drm/xe/guc: Add support for LNL firmware John.C.Harrison
2024-02-02 20:00 ` [PATCH v2 6/6] drm/xe/guc: define PVC FW John.C.Harrison
2024-02-03  6:09   ` Lucas De Marchi
2024-02-03  6:38     ` Lucas De Marchi
2024-02-02 20:06 ` ✓ CI.Patch_applied: success for Update to GuC 70.19.2 and add LNL Patchwork
2024-02-02 20:06 ` ✗ CI.checkpatch: warning " Patchwork
2024-02-02 20:07 ` ✓ CI.KUnit: success " Patchwork
2024-02-02 20:14 ` ✓ CI.Build: " Patchwork
2024-02-02 20:14 ` ✓ CI.Hooks: " Patchwork
2024-02-02 20:16 ` ✓ CI.checksparse: " Patchwork
2024-02-02 20:40 ` ✗ CI.BAT: failure " Patchwork

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=20240202200017.2133438-5-John.C.Harrison@Intel.com \
    --to=john.c.harrison@intel.com \
    --cc=Intel-Xe@Lists.FreeDesktop.Org \
    --cc=lucas.demarchi@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