Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "20200827055129.26566-1-shawn.c.lee@intel.com"
	<20200827055129.26566-1-shawn.c.lee@intel.com>
Cc: "Chiou, Cooper" <cooper.chiou@intel.com>,
	"Tseng, William" <william.tseng@intel.com>,
	"Nikula, Jani" <jani.nikula@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/fbc: disable FBC on Nightfury board
Date: Tue, 15 Sep 2020 16:35:25 +0300	[thread overview]
Message-ID: <20200915133525.GG6112@intel.com> (raw)
In-Reply-To: <BY5PR11MB43073FAD5FBBD0A47986E296A3200@BY5PR11MB4307.namprd11.prod.outlook.com>

On Tue, Sep 15, 2020 at 01:18:13PM +0000, Lee, Shawn C wrote:
> On Fri, Sept. 11, 2020, 2:21 p.m. Ville Syrjälä wrote:
> >On Thu, Aug 27, 2020 at 01:51:29PM +0800, Lee Shawn C wrote:
> >> Customer report random display flicker issue on Nightfury board.
> >> And we found this problem might be caused by VT-d and FBC are both 
> >> enabled. According to sighting report, it recommend to turn
> >> drm/i915/fbc: disable FBC on Nightfury board
> >> 
> >> Customer report random display flicker issue on Nightfury board.
> >> And we found this problem might be caused by VT-d and FBC are both 
> >> enabled. According to sighting report, it recommend to turn FBC off to 
> >> workaround this kind of issue.
> >> 
> >> This change refer to DMI BOARD_VENDOR and BOARD_NAME information to 
> >> disable FBC.
> >
> >What is this "nightfury board" exactly?
> 
> It is chrome os project on CML platform. The board name is "nightfury".

OK, then someone should definitely test if that missing w/a
fixes the underruns.

> 
> >
> >I think we're missing at least one fbc vs. vt-d w/a on some kbl/cfl/etc. era platforms:
> >git://github.com/vsyrjala/linux.git  vtd_wa_1142
> >
> >> 
> >> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> >> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> >> Cc: Jani Nikula <jani.nikula@intel.com>
> >> Cc: William Tseng <william.tseng@intel.com>
> >> Cc: Cooper Chiou <cooper.chiou@intel.com>
> >> Signed-off-by: Lee Shawn C <shawn.c.lee@intel.com>
> >> ---
> >>  drivers/gpu/drm/i915/display/intel_fbc.c | 22 ++++++++++++++++++++++
> >>  1 file changed, 22 insertions(+)
> >> 
> >> diff --git a/drivers/gpu/drm/i915/display/intel_fbc.c 
> >> b/drivers/gpu/drm/i915/display/intel_fbc.c
> >> index 327af428d73f..20660fdbab36 100644
> >> --- a/drivers/gpu/drm/i915/display/intel_fbc.c
> >> +++ b/drivers/gpu/drm/i915/display/intel_fbc.c
> >> @@ -39,6 +39,7 @@
> >>   */
> >>  
> >>  #include <drm/drm_fourcc.h>
> >> +#include <linux/dmi.h>
> >>  
> >>  #include "i915_drv.h"
> >>  #include "i915_trace.h"
> >> @@ -1439,6 +1440,24 @@ static int intel_sanitize_fbc_option(struct drm_i915_private *dev_priv)
> >>  	return 0;
> >>  }
> >>  
> >> +static int intel_fbc_vtd_callback(const struct dmi_system_id *id) {
> >> +	DRM_DEBUG_KMS("Disabling FBC to prevent screen flicker on %s device\n", id->ident);
> >> +	return 1;
> >> +}
> >> +
> >> +static const struct dmi_system_id intel_fbc_vtd_detect[] = {
> >> +	{
> >> +		.callback = intel_fbc_vtd_callback,
> >> +		.ident = "Google Nightfury",
> >> +		.matches = {
> >> +			DMI_MATCH(DMI_BOARD_VENDOR, "Google"),
> >> +			DMI_MATCH(DMI_BOARD_NAME, "Nightfury"),
> >> +		},
> >> +	},
> >> +	{ }
> >> +};
> >> +
> >>  static bool need_fbc_vtd_wa(struct drm_i915_private *dev_priv)  {
> >>  	/* WaFbcTurnOffFbcWhenHyperVisorIsUsed:skl,bxt */ @@ -1450,6 +1469,9 
> >> @@ static bool need_fbc_vtd_wa(struct drm_i915_private *dev_priv)
> >>  		return true;
> >>  	}
> >>  
> >> +	if (dmi_check_system(intel_fbc_vtd_detect))
> >> +		return true;
> >> +
> >>  	return false;
> >>  }
> >>  
> >> --
> >> 2.17.1
> >
> >--
> >Ville Syrjälä
> >Intel
> 
> Best regards,
> Shawn

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

  reply	other threads:[~2020-09-15 13:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-27  5:51 [Intel-gfx] [PATCH] drm/i915/fbc: disable FBC on Nightfury board Lee Shawn C
2020-08-27  6:31 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-08-27  8:28 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-09-11 13:48 ` [Intel-gfx] [PATCH v2] " Lee Shawn C
2020-09-11 14:21 ` [Intel-gfx] [PATCH] " Ville Syrjälä
2020-09-15 13:18   ` Lee, Shawn C
2020-09-15 13:35     ` Ville Syrjälä [this message]
2020-09-21 13:15       ` Lee, Shawn C
2020-09-11 14:45 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/fbc: disable FBC on Nightfury board (rev2) Patchwork
2020-09-11 17:47 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2020-09-21 13:09 [Intel-gfx] [PATCH] drm/i915/fbc: disable FBC on Nightfury board Lee, Shawn C

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=20200915133525.GG6112@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=20200827055129.26566-1-shawn.c.lee@intel.com \
    --cc=cooper.chiou@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=william.tseng@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