All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shankar, Uma" <uma.shankar@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915: Disable DSB usage for now
Date: Thu, 18 Nov 2021 19:40:48 +0000	[thread overview]
Message-ID: <ede57d2d0f3d446b9e5e047722830625@intel.com> (raw)
In-Reply-To: <20211014181856.17581-2-ville.syrjala@linux.intel.com>



> -----Original Message-----
> From: Intel-gfx <intel-gfx-bounces@lists.freedesktop.org> On Behalf Of Ville Syrjala
> Sent: Thursday, October 14, 2021 11:49 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH 2/2] drm/i915: Disable DSB usage for now
> 
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> Turns out the DSB has trouble correctly loading the gamma LUT.
> From a cursory look maybe like some entries do not load properly, or they get
> loaded with some gibberish. Unfortunately our current kms_color/etc. tests do not
> seem to catch this.
> 
> I had a brief look at the generated DSB batch and it looked correct. Tried a few quick
> tricks like writing the index register twice/etc. but didn't see any improvement.
> Also tried switching to the 10bit gamma mode in case there is yet another issue with
> the multi-segment mode, but even the 10bit mode was showing issues.
> 
> Switching to mmio fixes all of it. I suppose one theory is that maybe the DSB bangs
> on the LUT too quickly and it can't keep up and instead some data either gets
> dropped or corrupted. To confirm that someone should try to slow down the DSB's
> progress a bit.
> Another thought was that maybe the LUT has crappy dual porting and you get
> contention if you try to load it during active scanout. But why then would the mmio
> path work, unless it's just sufficiently slow?
> 
> Whatever the case, this is currently busted so let's disable it until we get to the root
> of the problem.

DSB functionally should work, as no potential hw issue is identified. We may have to
handle it better in driver. With this under investigation, we can disable it for now while
the fix is getting identified.

Reviewed-by: Uma Shankar <uma.shankar@intel.com>

> Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/3916
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
>  drivers/gpu/drm/i915/i915_pci.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_pci.c b/drivers/gpu/drm/i915/i915_pci.c index
> 7655c7a4f904..bfc7bdde73a1 100644
> --- a/drivers/gpu/drm/i915/i915_pci.c
> +++ b/drivers/gpu/drm/i915/i915_pci.c
> @@ -872,7 +872,7 @@ static const struct intel_device_info jsl_info = {
>  	TGL_CURSOR_OFFSETS, \
>  	.has_global_mocs = 1, \
>  	.has_pxp = 1, \
> -	.display.has_dsb = 1
> +	.display.has_dsb = 0 /* FIXME: LUT load is broken with DSB */
> 
>  static const struct intel_device_info tgl_info = {
>  	GEN12_FEATURES,
> --
> 2.32.0


  reply	other threads:[~2021-11-18 19:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14 18:18 [Intel-gfx] [PATCH 1/2] drm/i915: Declare .(de)gamma_lut_tests for icl+ Ville Syrjala
2021-10-14 18:18 ` [Intel-gfx] [PATCH 2/2] drm/i915: Disable DSB usage for now Ville Syrjala
2021-11-18 19:40   ` Shankar, Uma [this message]
2021-10-15  0:57 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [1/2] drm/i915: Declare .(de)gamma_lut_tests for icl+ Patchwork
2021-10-17 23:10 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915: Declare .(de)gamma_lut_tests for icl+ (rev2) Patchwork
2021-10-18  0:59 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-11-18 19:37 ` [Intel-gfx] [PATCH 1/2] drm/i915: Declare .(de)gamma_lut_tests for icl+ Shankar, Uma

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=ede57d2d0f3d446b9e5e047722830625@intel.com \
    --to=uma.shankar@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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.