All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/dmc: Update DG2 DMC version to v2.08
Date: Tue, 22 Nov 2022 16:19:18 -0500	[thread overview]
Message-ID: <Y3081s7c5ksutpMW@intel.com> (raw)
In-Reply-To: <Y304OGPuYRHAjQkx@mdroper-desk1.amr.corp.intel.com>

On Tue, Nov 22, 2022 at 12:59:36PM -0800, Matt Roper wrote:
> On Mon, Nov 21, 2022 at 06:18:15PM -0300, Gustavo Sousa wrote:
> > Release notes:
> > 
> > 1. Fixes for Register noclaims and few restore.
> > 
> > Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>
> 
> Now that we've removed force_probe from DG2, in general we're past the
> point where we can just directly update firmware versions like this; if
> someone has a working system with the current kernel + DMC 2.07 and then
> they update to a new kernel containing this patch (but without
> installing DMC 2.08), they'd see a regression.
> 
> In this case, maybe there's still time to sneak this specific update
> into -fixes so that it lands in the same kernel release that removes the
> force_probe protection on DG2?  But in general we need to start
> providing backwards-compatible support for all firmware updates going
> forward.  The GuC/HuC guys just went through an overhaul of their
> firmware handling to deal with this; we probably need something similar
> on the DMC side now too, although I suspect DMC should be simpler to
> deal with since most (all?) DMC firmwares are just drop-in replacements
> and there's no constantly changing firmware<->driver interface like
> there is with the GuC.
> 
> See Documentation/driver-api/firmware/firmware-usage-guidelines.rst for
> the official rules about firmware usage.

Matt is right here. But this update is an important fix and I will propagate
through the -fixes flow, so we don't need for now to support the 2.07 as
fallback. The 6.2 will be released only with the 2.08.

But please make sure you add a "Fixes:" tag to this patch. Then please
let us know when the fw file got accepted in the linux-firmware.git
so we can merge and propagate.

Moving forward we will need to support the fallback version like GuC,
or even better, remove the versioning from the filename entirely like
HuC.

> 
> 
> Matt
> 
> > ---
> >  drivers/gpu/drm/i915/display/intel_dmc.c | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/display/intel_dmc.c b/drivers/gpu/drm/i915/display/intel_dmc.c
> > index 081a4d0083b1..697196368fbb 100644
> > --- a/drivers/gpu/drm/i915/display/intel_dmc.c
> > +++ b/drivers/gpu/drm/i915/display/intel_dmc.c
> > @@ -52,8 +52,8 @@
> >  
> >  #define DISPLAY_VER12_DMC_MAX_FW_SIZE	ICL_DMC_MAX_FW_SIZE
> >  
> > -#define DG2_DMC_PATH			DMC_PATH(dg2, 2, 07)
> > -#define DG2_DMC_VERSION_REQUIRED	DMC_VERSION(2, 07)
> > +#define DG2_DMC_PATH			DMC_PATH(dg2, 2, 08)
> > +#define DG2_DMC_VERSION_REQUIRED	DMC_VERSION(2, 08)
> >  MODULE_FIRMWARE(DG2_DMC_PATH);
> >  
> >  #define ADLP_DMC_PATH			DMC_PATH(adlp, 2, 16)
> > -- 
> > 2.38.1
> > 
> 
> -- 
> Matt Roper
> Graphics Software Engineer
> VTT-OSGC Platform Enablement
> Intel Corporation

  reply	other threads:[~2022-11-22 21:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-21 21:18 [Intel-gfx] [PATCH] drm/i915/dmc: Update DG2 DMC version to v2.08 Gustavo Sousa
2022-11-21 21:46 ` Tolakanahalli Pradeep, Madhumitha
2022-11-21 22:26 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " Patchwork
2022-11-22  5:15 ` [Intel-gfx] [PATCH] " kernel test robot
2022-11-22 11:18 ` kernel test robot
2022-11-22 20:59 ` Matt Roper
2022-11-22 21:19   ` Rodrigo Vivi [this message]
2022-11-30 13:46     ` Gustavo Sousa

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=Y3081s7c5ksutpMW@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=matthew.d.roper@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 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.