From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 1/3] drm/xe: Remove ci-only GuC FW definitions
Date: Tue, 19 Dec 2023 17:58:40 -0500 [thread overview]
Message-ID: <ZYIgIBhBiIEQH6db@intel.com> (raw)
In-Reply-To: <20231219200023.2502159-1-daniele.ceraolospurio@intel.com>
On Tue, Dec 19, 2023 at 12:00:20PM -0800, Daniele Ceraolo Spurio wrote:
> As part of the FW definitions, we declare each blob as required via the
> MODULE_FIRMWARE() macro. This causes the initramfs update (or equivalent
> process) to look for the blobs on disk when the kernel is installed;
> therefore, we need to make sure that all FWs we define are available in
> linux-firmware.
>
> We currently don't plan to push the PVC blob to linux-firmware, while the
> LNL one will only be pushed once we have machines in CI to test it, so we
> need to remove them from the list for now.
>
> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
For the series:
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
and including it right now as part a respin for the pull-request
> ---
>
> This patch is intended to be added to the PR sent for drm-next, with the
> FW definitions being added to topic/core-for-CI afterwards by the other
> patches in this series.
>
> Note that this patch remove the last uses of the mmp FWs, but the
> support for those has been left in because we do plan to use mmp tags
> for early FW drops in the CI branch.
>
> drivers/gpu/drm/xe/xe_uc_fw.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_uc_fw.c b/drivers/gpu/drm/xe/xe_uc_fw.c
> index 73d6938c921d..9dff96dfe455 100644
> --- a/drivers/gpu/drm/xe/xe_uc_fw.c
> +++ b/drivers/gpu/drm/xe/xe_uc_fw.c
> @@ -102,9 +102,7 @@ struct fw_blobs_by_type {
> };
>
> #define XE_GUC_FIRMWARE_DEFS(fw_def, mmp_ver, major_ver) \
> - fw_def(LUNARLAKE, mmp_ver(xe, guc, lnl, 70, 6, 8)) \
> fw_def(METEORLAKE, major_ver(i915, guc, mtl, 70, 7)) \
> - fw_def(PVC, mmp_ver(xe, guc, pvc, 70, 9, 1)) \
> fw_def(DG2, major_ver(i915, guc, dg2, 70, 5)) \
> fw_def(DG1, major_ver(i915, guc, dg1, 70, 5)) \
> fw_def(ALDERLAKE_N, major_ver(i915, guc, tgl, 70, 5)) \
> --
> 2.43.0
>
next prev parent reply other threads:[~2023-12-19 22:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 20:00 [PATCH v2 1/3] drm/xe: Remove ci-only GuC FW definitions Daniele Ceraolo Spurio
2023-12-19 20:00 ` [PATCH v2 2/3] drm/xe/guc: define PVC FW Daniele Ceraolo Spurio
2023-12-19 20:00 ` [PATCH v2 3/3] drm/xe/guc: define LNL FW Daniele Ceraolo Spurio
2023-12-19 20:03 ` ✓ CI.Patch_applied: success for series starting with [v2,1/3] drm/xe: Remove ci-only GuC FW definitions Patchwork
2023-12-19 20:03 ` ✓ CI.checkpatch: " Patchwork
2023-12-19 20:04 ` ✓ CI.KUnit: " Patchwork
2023-12-19 20:11 ` ✓ CI.Build: " Patchwork
2023-12-19 20:12 ` ✓ CI.Hooks: " Patchwork
2023-12-19 20:13 ` ✓ CI.checksparse: " Patchwork
2023-12-19 20:55 ` ✗ CI.BAT: failure " Patchwork
2023-12-19 22:58 ` Rodrigo Vivi [this message]
2024-01-04 11:58 ` ✓ CI.Patch_applied: success " Patchwork
2024-01-04 11:58 ` ✓ CI.checkpatch: " Patchwork
2024-01-04 11:59 ` ✓ CI.KUnit: " Patchwork
2024-01-04 12:07 ` ✓ CI.Build: " Patchwork
2024-01-04 12:07 ` ✓ CI.Hooks: " Patchwork
2024-01-04 12:08 ` ✓ CI.checksparse: " Patchwork
2024-01-04 12:43 ` ✓ CI.BAT: " Patchwork
2024-01-30 18:33 ` [PATCH v2 1/3] " Dixit, Ashutosh
2024-01-30 18:48 ` Daniele Ceraolo Spurio
2024-01-30 22:11 ` Dixit, Ashutosh
2024-01-30 22:29 ` Daniele Ceraolo Spurio
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=ZYIgIBhBiIEQH6db@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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