All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
	intel-gfx@lists.freedesktop.org,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH 2/2] drm/i915: Downgrade unknown CSR firmware warnings
Date: Mon, 19 Nov 2018 09:52:04 -0800	[thread overview]
Message-ID: <20181119175202.GB19415@intel.com> (raw)
In-Reply-To: <154262423639.7424.17775599470988744532@jlahtine-desk.ger.corp.intel.com>

On Mon, Nov 19, 2018 at 12:43:56PM +0200, Joonas Lahtinen wrote:
> Quoting Chris Wilson (2018-11-19 00:01:57)
> > Quoting Lucas De Marchi (2018-11-17 00:42:34)
> > > Like it was done in commit 9e180d9991dc ("drm/i915: Downgrade unknown
> > > firmware warnings") for huc and guc: downgrade CSR firmware warnings. If
> > > we have released no firmware yet for a platform, stop scaring the
> > > consumer and merely note its expected absence.
> > > 
> > > By simply removing the warning and early return we hit the condition
> > > with the appropriate message.
> > > 
> > > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > > Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> > > ---
> > >  drivers/gpu/drm/i915/intel_csr.c | 3 ---
> > >  1 file changed, 3 deletions(-)
> > > 
> > > diff --git a/drivers/gpu/drm/i915/intel_csr.c b/drivers/gpu/drm/i915/intel_csr.c
> > > index b4476d891fa3..a516697bf57d 100644
> > > --- a/drivers/gpu/drm/i915/intel_csr.c
> > > +++ b/drivers/gpu/drm/i915/intel_csr.c
> > > @@ -496,9 +496,6 @@ void intel_csr_ucode_init(struct drm_i915_private *dev_priv)
> > >                 csr->fw_path = BXT_CSR_PATH;
> > >                 csr->required_version = BXT_CSR_VERSION_REQUIRED;
> > >                 csr->max_fw_size = BXT_CSR_MAX_FW_SIZE;
> > > -       } else {
> > > -               MISSING_CASE(INTEL_REVID(dev_priv));
> > 
> > Wider question would be if MISSING_CASE should be CI only. It's meant to
> > be a warning for us to fix before alpha_support=0, and so should never
> > reach users or any production system, so the question is moot.
> 
> Especially with the changes into CI log level reporting, we'd have to
> actually notice the MISSING_CASE triggers from the inflow of other IGT
> warn levels.
> 
> MISSING_CASE triggering BUG if alpha_support flag is lifted might be
> enough of a hammer to drive the point home if we've missed some?

I believe that would be too noise that we would never have a reliable CI.
maybe even a chicken and egg for lifting alpha_support...

But for this patch:

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>



> 
> Regards, Joonas
> 
> > 
> > As we have a warning message then the MISSING_CASE is indeed
> > superfluous here, and the firmware has a different release schedule to
> > alpha_support so doesn't merit the tight coupling implied by
> > MISSING_CASE (imo).
> > 
> > Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> > -Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-11-19 17:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-17  0:42 [PATCH 1/2] drm/i915: allow to load DMC firmware on next gen Lucas De Marchi
2018-11-17  0:42 ` [PATCH 2/2] drm/i915: Downgrade unknown CSR firmware warnings Lucas De Marchi
2018-11-18 22:01   ` Chris Wilson
2018-11-19 10:43     ` Joonas Lahtinen
2018-11-19 17:52       ` Rodrigo Vivi [this message]
2018-11-21  9:29   ` Jani Nikula
2018-11-21 17:20     ` Rodrigo Vivi
2018-11-22  0:14     ` Lucas De Marchi
2018-11-17  1:15 ` ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915: allow to load DMC firmware on next gen Patchwork
2018-11-18 21:24 ` ✓ Fi.CI.BAT: success " Patchwork
2018-11-18 22:41 ` ✗ Fi.CI.IGT: failure " Patchwork
2018-11-19 17:50 ` [PATCH 1/2] " Rodrigo Vivi
2018-11-19 18:24 ` ✓ Fi.CI.BAT: success for series starting with [1/2] " Patchwork
2018-11-20  0:04 ` ✓ Fi.CI.IGT: " 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=20181119175202.GB19415@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=lucas.demarchi@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.