From: sashiko-bot@kernel.org
To: "Julia Filipchuk" <julia.filipchuk@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/guc: Test GuC v70.74.0 for MTL, DG2
Date: Thu, 20 Aug 2026 19:48:18 +0000 [thread overview]
Message-ID: <20260820194818.A07721F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260820193724.3048409-2-julia.filipchuk@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The patch replaces the major-versioned GuC firmware definitions (`guc_maj`) with exact minor-patch versions (`guc_mmp`) for MTL and DG2, which removes the fallback logic and breaks GuC initialization on standard systems.
--
--- Patch [1]: [PATCH] drm/i915/guc: Test GuC v70.74.0 for MTL, DG2 ---
commit b7bd03e4f394bb57a559e10784e9ef6e098b9d4e
Author: Julia Filipchuk <julia.filipchuk@intel.com>
drm/i915/guc: Test GuC v70.74.0 for MTL, DG2
This patch updates the GuC firmware version to 70.74.0 for MTL and DG2 platforms.
It replaces the major-versioned definitions with exact minor-patch version definitions.
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c b/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
> index 7fac97fe30a63..4901cb9cb4ca6 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
[ ... ]
> @@ -88,8 +88,8 @@ void intel_uc_fw_change_status(struct intel_uc_fw *uc_fw,
> * security fixes, etc. to be enabled.
> */
> #define INTEL_GUC_FIRMWARE_DEFS(fw_def, guc_maj, guc_mmp) \
> - fw_def(METEORLAKE, 0, guc_maj(mtl, 70, 53, 0)) \
> - fw_def(DG2, 0, guc_maj(dg2, 70, 53, 0)) \
> + fw_def(METEORLAKE, 0, guc_mmp(mtl, 70, 74, 0)) \
> + fw_def(DG2, 0, guc_mmp(dg2, 70, 74, 0)) \
[Severity: High]
In INTEL_GUC_FIRMWARE_DEFS(), does removing the guc_maj fallback entry cause
a regression by breaking GuC initialization on systems where the exact firmware
version 70.74.0 is not present?
To test a new version while maintaining compatibility, should the guc_mmp
definition be added alongside (before) the guc_maj definition, rather than
replacing it?
> fw_def(ALDERLAKE_P, 0, guc_maj(adlp, 70, 12, 1)) \
> fw_def(ALDERLAKE_P, 0, guc_mmp(adlp, 70, 1, 1)) \
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260820193724.3048409-2-julia.filipchuk@intel.com?part=1
next prev parent reply other threads:[~2026-08-20 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 19:37 [PATCH] drm/i915/guc: Test GuC v70.74.0 for MTL, DG2 Julia Filipchuk
2026-08-20 19:48 ` sashiko-bot [this message]
2026-08-20 21:18 ` ✓ i915.CI.BAT: success for " Patchwork
2026-08-21 2:34 ` ✗ i915.CI.Full: 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=20260820194818.A07721F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=julia.filipchuk@intel.com \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.