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 11:59:59 -0700 [thread overview]
Message-ID: <20151014185959.GB7042@H87M> (raw)
In-Reply-To: <20151014122223.GU26517@intel.com>
On Wed, Oct 14, 2015 at 03:22:23PM +0300, Ville Syrjälä wrote:
> On Wed, Oct 14, 2015 at 01:12:27PM +0100, Chris Wilson wrote:
> > On Wed, Oct 14, 2015 at 03:07:41PM +0300, Ville Syrjälä wrote:
> > > On Tue, Oct 13, 2015 at 02:24:41PM -0700, Kevin Strasser wrote:
[...]
> > > > - I915_WRITE(reg, 0);
> > > > + I915_WRITE(reg, I915_READ(reg) & ~DISPLAY_PLANE_ENABLE);
> > >
> > > Eh, what now? We've been trying to eliminate these nasty RMWs.
> > >
> > > Are you saying that if we disabled the plane, but leave the "pass plane
> > > data through gamma" it still affects the output for any pixel "covered"
> > > by the disabled plane?
> >
> > What I thought was being said was that if a plane is set to black (but
> > with gamma enabled on the pipe) then a different CRC is produced
> > compared to when the pipe is completely disabled (no plane at all). It
> > sounded to me like a test case failure.
>
> In that case I don't understand how the patch is supposed to help.
>
> But yeah, tests like these should really set up an identity gamma
> and pipe csc matrix.
>
> Also we should grow some properties to control whether the plane
> data passes through the gamma/csc or not. Those could then be used
> to achieeve the same effect.
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. 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.
Understood, RMWs are inappropriate here. I'll rework the patch to explicitly
enable the bits that are needed.
Thanks,
Kevin
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-10-14 18:59 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 [this message]
2015-10-14 19:48 ` Ville Syrjälä
2015-10-14 20:33 ` Kevin Strasser
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=20151014185959.GB7042@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