Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Julia Filipchuk <julia.filipchuk@intel.com>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH 4/8] drm/xe/guc: Recommend GuC v70.53.0 for MTL, DG2, LNL
Date: Mon, 1 Dec 2025 15:00:08 -0800	[thread overview]
Message-ID: <4f3fb4f2-c322-48a3-9dae-dc80e4ea1168@intel.com> (raw)
In-Reply-To: <20251125014134.2075988-14-julia.filipchuk@intel.com>



On 11/24/2025 5:41 PM, Julia Filipchuk wrote:
> UAPI compatibility version 1.26.0
>
> Update recommended GuC version for MTL, DG2, LNL.
>
> Signed-off-by: Julia Filipchuk <julia.filipchuk@intel.com>

Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>

Daniele

> ---
>   drivers/gpu/drm/xe/xe_uc_fw.c | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_uc_fw.c b/drivers/gpu/drm/xe/xe_uc_fw.c
> index 622b76078567..810709f106e7 100644
> --- a/drivers/gpu/drm/xe/xe_uc_fw.c
> +++ b/drivers/gpu/drm/xe/xe_uc_fw.c
> @@ -117,9 +117,9 @@ struct fw_blobs_by_type {
>   #define XE_GUC_FIRMWARE_DEFS(fw_def, mmp_ver, major_ver)					\
>   	fw_def(PANTHERLAKE,	GT_TYPE_ANY,	major_ver(xe,	guc,	ptl,	70, 49, 4))	\
>   	fw_def(BATTLEMAGE,	GT_TYPE_ANY,	major_ver(xe,	guc,	bmg,	70, 49, 4))	\
> -	fw_def(LUNARLAKE,	GT_TYPE_ANY,	major_ver(xe,	guc,	lnl,	70, 45, 2))	\
> -	fw_def(METEORLAKE,	GT_TYPE_ANY,	major_ver(i915,	guc,	mtl,	70, 44, 1))	\
> -	fw_def(DG2,		GT_TYPE_ANY,	major_ver(i915,	guc,	dg2,	70, 45, 2))	\
> +	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(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))	\
>   	fw_def(ALDERLAKE_P,	GT_TYPE_ANY,	major_ver(i915,	guc,	adlp,	70, 44, 1))	\


  reply	other threads:[~2025-12-01 23:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25  1:41 [PATCH 0/8] drm/xe/guc: Recommend newer GuC firmware Julia Filipchuk
2025-11-25  1:41 ` [PATCH 1/8] Revert "topic/for-xe-CI: drm/xe/cri: Define GuC firmware for CRI" Julia Filipchuk
2025-11-25  1:41 ` [PATCH 2/8] Revert "drm/xe/nvls: Define GuC firmware for NVL-S" Julia Filipchuk
2025-11-25  1:41 ` [PATCH 3/8] Revert "drm/xe/pvc: Add GuC firmware definition" Julia Filipchuk
2025-11-25  1:41 ` [PATCH 4/8] drm/xe/guc: Recommend GuC v70.53.0 for MTL, DG2, LNL Julia Filipchuk
2025-12-01 23:00   ` Daniele Ceraolo Spurio [this message]
2025-11-25  1:41 ` [PATCH 5/8] drm/xe/guc: Recommend GuC v70.54.0 for BMG, PTL Julia Filipchuk
2025-12-01 23:00   ` Daniele Ceraolo Spurio
2025-11-25  1:41 ` [PATCH 6/8] drm/xe/pvc: Add GuC firmware definition Julia Filipchuk
2025-11-25  1:41 ` [PATCH 7/8] drm/xe/nvls: Define GuC firmware for NVL-S Julia Filipchuk
2025-11-25  1:41 ` [PATCH 8/8] topic/for-xe-CI: drm/xe/cri: Define GuC firmware for CRI Julia Filipchuk
2025-11-25  9:58 ` ✓ CI.KUnit: success for drm/xe/guc: Recommend newer GuC firmware Patchwork
2025-11-25 10:33 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-25 13:48 ` ✗ Xe.CI.Full: failure " Patchwork
2025-11-25 19:17   ` 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=4f3fb4f2-c322-48a3-9dae-dc80e4ea1168@intel.com \
    --to=daniele.ceraolospurio@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=julia.filipchuk@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