From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [PATCH v2 2/3] drm/xe/guc: define PVC FW
Date: Tue, 19 Dec 2023 12:00:21 -0800 [thread overview]
Message-ID: <20231219200023.2502159-2-daniele.ceraolospurio@intel.com> (raw)
In-Reply-To: <20231219200023.2502159-1-daniele.ceraolospurio@intel.com>
Add PVC GuC FW definition. This is patch is for CI-only and it is meant
for the topic/core-for-CI branch.
Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
---
drivers/gpu/drm/xe/xe_uc_fw.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/xe/xe_uc_fw.c b/drivers/gpu/drm/xe/xe_uc_fw.c
index 9dff96dfe455..92940199ba4a 100644
--- a/drivers/gpu/drm/xe/xe_uc_fw.c
+++ b/drivers/gpu/drm/xe/xe_uc_fw.c
@@ -103,6 +103,7 @@ struct fw_blobs_by_type {
#define XE_GUC_FIRMWARE_DEFS(fw_def, mmp_ver, major_ver) \
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 20:00 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 ` Daniele Ceraolo Spurio [this message]
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 ` [PATCH v2 1/3] " Rodrigo Vivi
2024-01-04 11:58 ` ✓ CI.Patch_applied: success for series starting with [v2,1/3] " 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=20231219200023.2502159-2-daniele.ceraolospurio@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=rodrigo.vivi@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