public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: <intel-gfx@lists.freedesktop.org>, <dri-devel@lists.freedesktop.org>
Subject: [Intel-gfx] [PATCH 0/3] Update firmware to v62.0.0
Date: Tue, 15 Jun 2021 17:12:59 -0700	[thread overview]
Message-ID: <20210616001302.84233-1-matthew.brost@intel.com> (raw)

As part of enabling GuC submission [1] we need to update to the latest
and greatest firmware. This series does that. All backwards
compatibility breaking changes squashed into a single patch #2. Same
series sent to trybot [2] forcing GuC to be enabled to ensure we haven't
broke something.

v2: Address comments, looking for remaning RBs so patches can be
squashed and sent for CI
v3: Delete a few unused defines, squash patches
v4: Add values back into kernel doc, fix docs warning

Signed-off-by: Matthew Brost <matthew.brost@intel.com>

[1] https://patchwork.freedesktop.org/series/89844
[2] https://patchwork.freedesktop.org/series/91341 

Michal Wajdeczko (3):
  drm/i915/guc: Introduce unified HXG messages
  drm/i915/guc: Update firmware to v62.0.0
  drm/i915/doc: Include GuC ABI documentation

 Documentation/gpu/i915.rst                    |   8 +
 .../gpu/drm/i915/gt/uc/abi/guc_actions_abi.h  | 107 ++++++
 .../gt/uc/abi/guc_communication_ctb_abi.h     | 126 +++++--
 .../gt/uc/abi/guc_communication_mmio_abi.h    |  65 ++--
 .../gpu/drm/i915/gt/uc/abi/guc_messages_abi.h | 213 +++++++++++
 drivers/gpu/drm/i915/gt/uc/intel_guc.c        | 107 ++++--
 drivers/gpu/drm/i915/gt/uc/intel_guc_ads.c    |  45 +--
 drivers/gpu/drm/i915/gt/uc/intel_guc_ct.c     | 356 +++++++++---------
 drivers/gpu/drm/i915/gt/uc/intel_guc_ct.h     |   6 +-
 drivers/gpu/drm/i915/gt/uc/intel_guc_fwif.h   |  75 +---
 drivers/gpu/drm/i915/gt/uc/intel_guc_log.c    |  29 +-
 drivers/gpu/drm/i915/gt/uc/intel_guc_log.h    |   6 +-
 drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c      |  26 +-
 13 files changed, 748 insertions(+), 421 deletions(-)

-- 
2.28.0

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2021-06-15 23:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16  0:12 Matthew Brost [this message]
2021-06-16  0:13 ` [Intel-gfx] [PATCH 1/3] drm/i915/guc: Introduce unified HXG messages Matthew Brost
2021-06-16  0:13 ` [Intel-gfx] [PATCH 2/3] drm/i915/guc: Update firmware to v62.0.0 Matthew Brost
2021-06-17  1:41   ` Daniele Ceraolo Spurio
2021-06-17  6:24     ` Michal Wajdeczko
2021-06-16  0:13 ` [Intel-gfx] [PATCH 3/3] drm/i915/doc: Include GuC ABI documentation Matthew Brost
2021-06-16  0:20 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Update firmware to v62.0.0 (rev4) Patchwork
2021-06-16  0:22 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-06-16  0:49 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-06-16  6:04 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-06-18 22:38   ` Matt Roper
2021-06-16 15:16 ` [Intel-gfx] [PATCH 0/3] Update firmware to v62.0.0 Mike Lothian
  -- strict thread matches above, loose matches on Subject: below --
2021-06-14 19:42 Matthew Brost

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=20210616001302.84233-1-matthew.brost@intel.com \
    --to=matthew.brost@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