From: "Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>
To: <John.C.Harrison@Intel.com>, <Intel-GFX@Lists.FreeDesktop.Org>
Cc: Tomasz Mistat <tomasz.mistat@intel.com>, DRI-Devel@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915/dg2: Define GuC firmware version for DG2
Date: Wed, 27 Apr 2022 17:24:44 -0700 [thread overview]
Message-ID: <7970427c-485e-6a60-2925-a5b3cd75df6a@intel.com> (raw)
In-Reply-To: <20220427165550.3636686-3-John.C.Harrison@Intel.com>
On 4/27/2022 9:55 AM, John.C.Harrison@Intel.com wrote:
> From: John Harrison <John.C.Harrison@Intel.com>
>
> First release of GuC for DG2.
Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Daniele
>
> Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
> CC: Tomasz Mistat <tomasz.mistat@intel.com>
> CC: Ramalingam C <ramalingam.c@intel.com>
> CC: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> ---
> drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 1 +
> 1 file changed, 1 insertion(+)
>
> 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 a876d39e6bcf..d078f884b5e3 100644
> --- a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
> +++ b/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
> @@ -53,6 +53,7 @@ void intel_uc_fw_change_status(struct intel_uc_fw *uc_fw,
> * firmware as TGL.
> */
> #define INTEL_GUC_FIRMWARE_DEFS(fw_def, guc_def) \
> + fw_def(DG2, 0, guc_def(dg2, 70, 1, 2)) \
> fw_def(ALDERLAKE_P, 0, guc_def(adlp, 70, 1, 1)) \
> fw_def(ALDERLAKE_S, 0, guc_def(tgl, 70, 1, 1)) \
> fw_def(DG1, 0, guc_def(dg1, 70, 1, 1)) \
next prev parent reply other threads:[~2022-04-28 0:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 16:55 [Intel-gfx] [PATCH 0/2] Initial GuC firmware release for DG2 John.C.Harrison
2022-04-27 16:55 ` [Intel-gfx] [PATCH 1/2] Revert "drm/i915/dg2: Define GuC firmware version for DG2" John.C.Harrison
2022-04-27 16:55 ` [Intel-gfx] [PATCH 2/2] drm/i915/dg2: Define GuC firmware version for DG2 John.C.Harrison
2022-04-28 0:24 ` Ceraolo Spurio, Daniele [this message]
2022-04-27 17:37 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Initial GuC firmware release " Patchwork
2022-04-27 18:24 ` [Intel-gfx] [PATCH 0/2] " Timo Aaltonen
2022-04-27 22:14 ` John Harrison
2022-04-28 5:52 ` Lucas De Marchi
2022-04-27 18:59 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
2022-04-28 0:01 ` John Harrison
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=7970427c-485e-6a60-2925-a5b3cd75df6a@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 \
--cc=tomasz.mistat@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