public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Kevin Strasser <kevin.strasser@linux.intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: respect previous reg values on primary plane disable
Date: Wed, 14 Oct 2015 13:33:57 -0700	[thread overview]
Message-ID: <20151014203357.GC7042@H87M> (raw)
In-Reply-To: <20151014194852.GA26517@intel.com>

On Wed, Oct 14, 2015 at 10:48:52PM +0300, Ville Syrjälä wrote:
> On Wed, Oct 14, 2015 at 11:59:59AM -0700, Kevin Strasser wrote:
[...]
> > Just to level set, these cases will produce different CRCs on HSW:
> >  1. Primary plane disabled, gamma correction disabled
> >  2. Primary plane disabled, gamma correction enabled
> > 
> > Case 2 is visibly brighter than case 1 and looks more like the enabled black
> > primary plane case.
> 
> Ugh. That's weird. I thought data not going through any plane would
> bypass the gamma too.
> 
> > The purpose of this patch is to get the behavior of a
> > disabled primary plane to match that of an enabled black plane, just as it does
> > on non-HSW platforms.
> 
> Does it? I just tried it on IVB, and behaves just like you said. So not
> sure how far back this goes.

Ah, so this test case is failing on IVB too? Are there any reporting tools we
can look at to find out what tests are passing for each platform?

> And now I'm really wondering about platforms where the primary
> plane need not be fullscreen (gen2/3 and chv).
> 
> I tried this on SKL too, but that confused me even more. The data not
> going through any plane seems to be gamma corrected regardless of any
> plane control bits, so that's good. However the legacy palette seems
> all fubar. Black input apparently doesn't map to palette entry 0.
> I wonder if you're seeing this on HSW too, or is your palette entry 0
> supposed to be non-black?

I also tried on BDW and it is passing the test with and without my patch
applied.

I'm not really sure what 'palette entry 0' you are looking for. Could you point
me to where in the code I can find out?

> Looks like quite a bit more testing is needed to get to the bottom of
> this.

Agreed, this does seem to extend beyond HSW. For now do you think my patch is
the right approach at least for HSW alone?

Thanks,
Kevin
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-10-14 20:33 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-13 21:24 [PATCH] drm/i915: respect previous reg values on primary plane disable Kevin Strasser
2015-10-13 23:02 ` Jesse Barnes
2015-10-14  7:58 ` Jani Nikula
2015-10-14  7:59   ` Jani Nikula
2015-10-14 18:44   ` Kevin Strasser
2015-10-14 19:01     ` Daniel Vetter
2015-10-14 12:07 ` Ville Syrjälä
2015-10-14 12:12   ` Chris Wilson
2015-10-14 12:22     ` Ville Syrjälä
2015-10-14 18:59       ` Kevin Strasser
2015-10-14 19:48         ` Ville Syrjälä
2015-10-14 20:33           ` Kevin Strasser [this message]
2015-10-15  8:20             ` Ville Syrjälä
2015-10-15 23:00               ` Kevin Strasser
2015-10-16  0:14                 ` Ville Syrjälä
2015-10-14 13:04   ` Daniel Vetter
2015-10-14 13:09     ` Ville Syrjälä
2015-10-14 22:51 ` [PATCH v2] drm/i915/hsw: keep gamma and CSC enabled for " Kevin Strasser
2015-10-15 12:31   ` Daniel Vetter
2015-10-15 12:41     ` Ville Syrjälä
2015-10-16 22:53       ` Bob Paauwe
2015-10-19 10:15         ` Daniel Vetter
2015-10-19 17:13           ` Kevin Strasser
2015-10-20 15:48             ` Bob Paauwe
2015-10-20 16:13               ` Ville Syrjälä
2015-10-20 17:00                 ` Bob Paauwe
2015-10-21  6:31                   ` Daniel Vetter
2015-10-20 15:49   ` Bob Paauwe

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=20151014203357.GC7042@H87M \
    --to=kevin.strasser@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox