From: "Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>
To: <John.C.Harrison@Intel.com>, <Intel-GFX@Lists.FreeDesktop.Org>
Cc: DRI-Devel@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH v3 3/3] drm/i915/uc: Enable version reduced firmware files for newest platforms
Date: Tue, 6 Sep 2022 13:29:55 -0700 [thread overview]
Message-ID: <1f200f90-0451-b7b3-e2f0-598c17e6b274@intel.com> (raw)
In-Reply-To: <20220827011702.3465334-4-John.C.Harrison@Intel.com>
On 8/26/2022 6:17 PM, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
>
> Going forwards, the intention is for GuC firmware files to be named
> for their major version only and HuC firmware files to have no version
> number in the name at all. This patch adds those entries for DG1/2 and
> ADL-P/S.
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
However, looks like a new GuC minor version might land in the next
couple of days, so IMO better wait until that is confirmed before
merging this so we can do a single pull request to linux-firmware.
Daniele
> ---
> drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> 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 af425916cdf64..78b1198bcf39b 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
> @@ -72,11 +72,14 @@ 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(DG2, 0, guc_mmp(dg2, 70, 4, 1)) \
> + fw_def(DG2, 0, guc_maj(dg2, 70, 4)) \
> + fw_def(ALDERLAKE_P, 0, guc_maj(adlp, 70, 1)) \
> fw_def(ALDERLAKE_P, 0, guc_mmp(adlp, 70, 1, 1)) \
> fw_def(ALDERLAKE_P, 0, guc_mmp(adlp, 69, 0, 3)) \
> + fw_def(ALDERLAKE_S, 0, guc_maj(tgl, 70, 1)) \
> fw_def(ALDERLAKE_S, 0, guc_mmp(tgl, 70, 1, 1)) \
> fw_def(ALDERLAKE_S, 0, guc_mmp(tgl, 69, 0, 3)) \
> + fw_def(DG1, 0, guc_maj(dg1, 70, 1)) \
> fw_def(DG1, 0, guc_mmp(dg1, 70, 1, 1)) \
> fw_def(ROCKETLAKE, 0, guc_mmp(tgl, 70, 1, 1)) \
> fw_def(TIGERLAKE, 0, guc_mmp(tgl, 70, 1, 1)) \
> @@ -92,8 +95,11 @@ void intel_uc_fw_change_status(struct intel_uc_fw *uc_fw,
> fw_def(SKYLAKE, 0, guc_mmp(skl, 70, 1, 1))
>
> #define INTEL_HUC_FIRMWARE_DEFS(fw_def, huc_raw, huc_mmp) \
> + fw_def(ALDERLAKE_P, 0, huc_raw(tgl)) \
> fw_def(ALDERLAKE_P, 0, huc_mmp(tgl, 7, 9, 3)) \
> + fw_def(ALDERLAKE_S, 0, huc_raw(tgl)) \
> fw_def(ALDERLAKE_S, 0, huc_mmp(tgl, 7, 9, 3)) \
> + fw_def(DG1, 0, huc_raw(dg1)) \
> fw_def(DG1, 0, huc_mmp(dg1, 7, 9, 3)) \
> fw_def(ROCKETLAKE, 0, huc_mmp(tgl, 7, 9, 3)) \
> fw_def(TIGERLAKE, 0, huc_mmp(tgl, 7, 9, 3)) \
next prev parent reply other threads:[~2022-09-06 20:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-27 1:16 [Intel-gfx] [PATCH v3 0/3] Drop version numbers from firmware files John.C.Harrison
2022-08-27 1:17 ` [Intel-gfx] [PATCH v3 1/3] drm/i915/uc: Support for version reduced and multiple " John.C.Harrison
2022-08-27 1:17 ` [Intel-gfx] [PATCH v3 2/3] drm/i915/uc: Add patch level version number support John.C.Harrison
2022-09-06 20:27 ` Ceraolo Spurio, Daniele
2022-08-27 1:17 ` [Intel-gfx] [PATCH v3 3/3] drm/i915/uc: Enable version reduced firmware files for newest platforms John.C.Harrison
2022-09-06 20:29 ` Ceraolo Spurio, Daniele [this message]
2022-09-07 16:58 ` Ceraolo Spurio, Daniele
2022-08-27 1:45 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Drop version numbers from firmware files (rev4) Patchwork
2022-08-27 1:45 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-08-27 2:05 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-08-30 18:30 ` [Intel-gfx] ✗ Fi.CI.IGT: 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=1f200f90-0451-b7b3-e2f0-598c17e6b274@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=DRI-Devel@Lists.FreeDesktop.Org \
--cc=Intel-GFX@Lists.FreeDesktop.Org \
--cc=John.C.Harrison@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