All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [CI 0/4] drm/i915: GSC FW support for MTL
Date: Mon, 12 Jun 2023 11:15:25 -0700	[thread overview]
Message-ID: <20230612181529.2222451-1-daniele.ceraolospurio@intel.com> (raw)

Last chunk of the required support for the GSC FW. This includes some
fixes to the GSC memory allocation, FW idefinition and version
management, plus a new debugfs for debug information.

The FW team has asked to not send the current FW blob to
linux-firmware yet, as they're planning some updates. Therefore, the
FW definition patch will be sent separately and merged to the
topic/core-for-CI branch.
The series has already been tested with the FW definition patch applied
(see CI results on previous rev), so this is a re-send for CI to make
sure everything works without that patch before merging.

Daniele Ceraolo Spurio (4):
  drm/i915/gsc: fixes and updates for GSC memory allocation
  drm/i915/mtl/gsc: extract release and security versions from the gsc
    binary
  drm/i915/mtl/gsc: query the GSC FW for its compatibility version
  drm/i915/mtl/gsc: Add a gsc_info debugfs

 drivers/gpu/drm/i915/Makefile                 |   3 +-
 .../drm/i915/gt/uc/intel_gsc_binary_headers.h |  75 ++++-
 drivers/gpu/drm/i915/gt/uc/intel_gsc_fw.c     | 307 +++++++++++++++---
 drivers/gpu/drm/i915/gt/uc/intel_gsc_fw.h     |   2 +
 drivers/gpu/drm/i915/gt/uc/intel_gsc_uc.c     | 124 ++++++-
 drivers/gpu/drm/i915/gt/uc/intel_gsc_uc.h     |  21 ++
 .../gpu/drm/i915/gt/uc/intel_gsc_uc_debugfs.c |  39 +++
 .../gpu/drm/i915/gt/uc/intel_gsc_uc_debugfs.h |  14 +
 .../i915/gt/uc/intel_gsc_uc_heci_cmd_submit.h |   1 +
 drivers/gpu/drm/i915/gt/uc/intel_huc.c        |   6 +-
 drivers/gpu/drm/i915/gt/uc/intel_huc_fw.c     |  13 +-
 drivers/gpu/drm/i915/gt/uc/intel_uc_debugfs.c |   2 +
 drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c      |  80 +++--
 drivers/gpu/drm/i915/gt/uc/intel_uc_fw.h      |   4 +
 drivers/gpu/drm/i915/i915_reg.h               |  26 +-
 15 files changed, 615 insertions(+), 102 deletions(-)
 create mode 100644 drivers/gpu/drm/i915/gt/uc/intel_gsc_uc_debugfs.c
 create mode 100644 drivers/gpu/drm/i915/gt/uc/intel_gsc_uc_debugfs.h

-- 
2.40.0


             reply	other threads:[~2023-06-12 18:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 18:15 Daniele Ceraolo Spurio [this message]
2023-06-12 18:15 ` [Intel-gfx] [CI 1/4] drm/i915/gsc: fixes and updates for GSC memory allocation Daniele Ceraolo Spurio
2023-06-12 18:15 ` [Intel-gfx] [CI 2/4] drm/i915/mtl/gsc: extract release and security versions from the gsc binary Daniele Ceraolo Spurio
2023-06-12 18:15 ` [Intel-gfx] [CI 3/4] drm/i915/mtl/gsc: query the GSC FW for its compatibility version Daniele Ceraolo Spurio
2023-06-12 18:15 ` [Intel-gfx] [CI 4/4] drm/i915/mtl/gsc: Add a gsc_info debugfs Daniele Ceraolo Spurio
2023-06-12 20:03 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: GSC FW support for MTL (rev4) Patchwork
2023-06-12 20:03 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-06-12 20:17 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-06-13  5:29 ` [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=20230612181529.2222451-1-daniele.ceraolospurio@intel.com \
    --to=daniele.ceraolospurio@intel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.