intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: 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: Wed, 21 Nov 2018 09:20:29 -0800	[thread overview]
Message-ID: <20181121172029.GB4587@intel.com> (raw)
In-Reply-To: <871s7eg4o1.fsf@intel.com>

On Wed, Nov 21, 2018 at 11:29:02AM +0200, Jani Nikula wrote:
> On Fri, 16 Nov 2018, Lucas De Marchi <lucas.demarchi@intel.com> wrote:
> > 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>
> 
> *sigh*

ops, I just noticed that I forgot to reply here yesterday after
merging these to dinq. :/

> 
> This patch would not have been needed at all with patch 1/2.
> 
> The point was that we shouldn't proceed without the max fw size
> set. Even with the module parameter. Because that would fail at the
> firmware loading stage later.
> 
> If the warn was such a big deal, it should've been changed to a debug
> message with an early return, not removed.

hmmm... that's a good point...

> 
> BR,
> Jani.
> 
> 
> > ---
> >  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));
> > -		return;
> >  	}
> >  
> >  	if (i915_modparams.dmc_firmware_path) {
> 
> -- 
> Jani Nikula, Intel Open Source Graphics Center
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-11-21 17:20 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
2018-11-21  9:29   ` Jani Nikula
2018-11-21 17:20     ` Rodrigo Vivi [this message]
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=20181121172029.GB4587@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@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 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 NNTP newsgroup(s).