From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "dri-devel@lists.freedesktop.org" <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v2 2/5] drm/i915/mtl/gsc: extract release and security versions from the gsc binary
Date: Thu, 8 Jun 2023 21:51:39 +0000 [thread overview]
Message-ID: <f003c4360ec8383388d25175e022e8d1d8e7eb26.camel@intel.com> (raw)
In-Reply-To: <20230606022402.2048235-3-daniele.ceraolospurio@intel.com>
Everything looks good to me, so
Reviewed-by: Alan Previn <alan.previn.teres.alexis@intel.com>
On Mon, 2023-06-05 at 19:23 -0700, Ceraolo Spurio, Daniele wrote:
> The release and security versions of the GSC binary are not used at
> runtime to decide interface compatibility (there is a separate version
> for that), but they're still useful for debug, so it is still worth
> extracting them and printing them out in dmesg.
alan:snip
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_gsc_binary_headers.h b/drivers/gpu/drm/i915/gt/uc/intel_gsc_binary_headers.h
> index 714f0c256118..ad80afcafd23 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_gsc_binary_headers.h
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_gsc_binary_headers.h
alan:snip
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_gsc_fw.c b/drivers/gpu/drm/i915/gt/uc/intel_gsc_fw.c
alan:snip
> @@ -42,6 +43,157 @@ bool intel_gsc_uc_fw_init_done(struct intel_gsc_uc *gsc)
alan:snip
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_gsc_fw.h b/drivers/gpu/drm/i915/gt/uc/intel_gsc_fw.h
alan:snip
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_gsc_uc.h b/drivers/gpu/drm/i915/gt/uc/intel_gsc_uc.h
alan:snip
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_huc_fw.c b/drivers/gpu/drm/i915/gt/uc/intel_huc_fw.c
alan:snip
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c b/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
alan:snip
> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.h b/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.h
alan:snip
> /*
> @@ -289,6 +290,8 @@ static inline u32 intel_uc_fw_get_upload_size(struct intel_uc_fw *uc_fw)
alan:snip
next prev parent reply other threads:[~2023-06-08 21:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 2:23 [Intel-gfx] [PATCH v2 0/5] drm/i915: GSC FW support for MTL Daniele Ceraolo Spurio
2023-06-06 2:23 ` [Intel-gfx] [PATCH v2 1/5] drm/i915/gsc: fixes and updates for GSC memory allocation Daniele Ceraolo Spurio
2023-06-07 19:22 ` Teres Alexis, Alan Previn
2023-06-06 2:23 ` [Intel-gfx] [PATCH v2 2/5] drm/i915/mtl/gsc: extract release and security versions from the gsc binary Daniele Ceraolo Spurio
2023-06-08 21:51 ` Teres Alexis, Alan Previn [this message]
2023-06-06 2:24 ` [Intel-gfx] [PATCH v2 3/5] drm/i915/mtl/gsc: query the GSC FW for its compatibility version Daniele Ceraolo Spurio
2023-06-08 23:36 ` Teres Alexis, Alan Previn
2023-06-06 2:24 ` [Intel-gfx] [PATCH v2 4/5] drm/i915/mtl/gsc: Add a gsc_info debugfs Daniele Ceraolo Spurio
2023-06-06 4:32 ` [Intel-gfx] [PATCH v3] " Daniele Ceraolo Spurio
2023-06-07 21:23 ` Teres Alexis, Alan Previn
2023-06-06 6:49 ` [Intel-gfx] [PATCH v2 4/5] " kernel test robot
2023-06-06 7:21 ` kernel test robot
2023-06-06 8:04 ` kernel test robot
2023-06-06 8:26 ` kernel test robot
2023-06-06 2:24 ` [Intel-gfx] [PATCH v2 5/5] drm/i915/gsc: define gsc fw Daniele Ceraolo Spurio
2023-06-06 2:53 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915: GSC FW support for MTL (rev2) Patchwork
2023-06-06 5:32 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: GSC FW support for MTL (rev3) Patchwork
2023-06-06 5:32 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-06-06 5:42 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-07 0:17 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=f003c4360ec8383388d25175e022e8d1d8e7eb26.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@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