dri-devel Archive mirror
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: intel-gfx@lists.freedesktop.org, daniele.ceraolospurio@intel.com,
	john.c.harrison@intel.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 00/13] Update firmware to v62.0.0
Date: Fri, 11 Jun 2021 11:46:27 -0700	[thread overview]
Message-ID: <20210611184627.GA29357@sdutt-i7> (raw)
In-Reply-To: <dce71640-7648-d321-c3e1-24e98a6276e9@intel.com>

On Thu, Jun 10, 2021 at 03:35:57PM +0200, Michal Wajdeczko wrote:
> 
> 
> On 10.06.2021 06:36, Matthew Brost wrote:
> > As part of enabling GuC submission [1] we need to update to the latest
> > and greatest firmware. This series does that. This is a destructive
> > change. e.g. Without all the patches in this series it will break the
> 
> not really 'all'
> 

Yea, typo. I updated the comment below to say 'most' but missed this one.

> > i915 driver. As such, after we review most of these patches they will
> > squashed into a single patch for merging.
> 
> I assume final series will looks as follows:
> 
> 1                      = hxg
> 2+3+5+6+7+8+4+10+11+13 = ctb/ads/fw
> 12                     = log
> 9                      = rst
>

Seems right to me.
 
> > 
> > v2: Address comments, looking for remaning RBs so patches can be
> 
> typo
>

Not seeing the typo.
 
> and likely series should be generated with -v 2 option too
>

Didn't know about -v2 option. Will use going forward.

Matt
 
> 
> > squashed and sent for CI
> > 
> > Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> > 
> > [1] https://patchwork.freedesktop.org/series/89844/i
> > 
> > John Harrison (3):
> >   drm/i915/guc: Support per context scheduling policies
> >   drm/i915/guc: Unified GuC log
> >   drm/i915/guc: Update firmware to v62.0.0
> > 
> > Michal Wajdeczko (10):
> >   drm/i915/guc: Introduce unified HXG messages
> >   drm/i915/guc: Update MMIO based communication
> >   drm/i915/guc: Update CTB response status definition
> >   drm/i915/guc: Add flag for mark broken CTB
> >   drm/i915/guc: New definition of the CTB descriptor
> >   drm/i915/guc: New definition of the CTB registration action
> >   drm/i915/guc: New CTB based communication
> >   drm/i915/doc: Include GuC ABI documentation
> >   drm/i915/guc: Kill guc_clients.ct_pool
> >   drm/i915/guc: Kill ads.client_info
> > 
> >  Documentation/gpu/i915.rst                    |   8 +
> >  .../gpu/drm/i915/gt/uc/abi/guc_actions_abi.h  | 107 ++++++
> >  .../gt/uc/abi/guc_communication_ctb_abi.h     | 128 +++++--
> >  .../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, 750 insertions(+), 421 deletions(-)
> > 

  reply	other threads:[~2021-06-11 18:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10  4:36 [PATCH 00/13] Update firmware to v62.0.0 Matthew Brost
2021-06-10  4:16 ` [Intel-gfx] " Matthew Brost
2021-06-10  4:36 ` [PATCH 01/13] drm/i915/guc: Introduce unified HXG messages Matthew Brost
2021-06-14 17:04   ` Daniele Ceraolo Spurio
2021-06-10  4:36 ` [PATCH 02/13] drm/i915/guc: Update MMIO based communication Matthew Brost
2021-06-14 18:11   ` Daniele Ceraolo Spurio
2021-06-10  4:36 ` [PATCH 03/13] drm/i915/guc: Update CTB response status definition Matthew Brost
2021-06-10  4:36 ` [PATCH 04/13] drm/i915/guc: Support per context scheduling policies Matthew Brost
2021-06-10  4:36 ` [PATCH 05/13] drm/i915/guc: Add flag for mark broken CTB Matthew Brost
2021-06-10  4:36 ` [PATCH 06/13] drm/i915/guc: New definition of the CTB descriptor Matthew Brost
2021-06-14 18:17   ` Daniele Ceraolo Spurio
2021-06-10  4:36 ` [PATCH 07/13] drm/i915/guc: New definition of the CTB registration action Matthew Brost
2021-06-14 18:21   ` Daniele Ceraolo Spurio
2021-06-10  4:36 ` [PATCH 08/13] drm/i915/guc: New CTB based communication Matthew Brost
2021-06-14 18:24   ` Daniele Ceraolo Spurio
2021-06-10  4:36 ` [PATCH 09/13] drm/i915/doc: Include GuC ABI documentation Matthew Brost
2021-06-10 13:55   ` [Intel-gfx] " Piotr Piórkowski
2021-06-10  4:36 ` [PATCH 10/13] drm/i915/guc: Kill guc_clients.ct_pool Matthew Brost
2021-06-10  4:36 ` [PATCH 11/13] drm/i915/guc: Kill ads.client_info Matthew Brost
2021-06-10  4:36 ` [PATCH 12/13] drm/i915/guc: Unified GuC log Matthew Brost
2021-06-10  4:36 ` [PATCH 13/13] drm/i915/guc: Update firmware to v62.0.0 Matthew Brost
2021-06-10 13:35 ` [PATCH 00/13] " Michal Wajdeczko
2021-06-11 18:46   ` Matthew Brost [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-06-07 18:03 Matthew Brost
2021-06-07 22:19 ` Daniele Ceraolo Spurio
2021-06-11 18:44   ` 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=20210611184627.GA29357@sdutt-i7 \
    --to=matthew.brost@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=john.c.harrison@intel.com \
    --cc=michal.wajdeczko@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).