All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Cc: Jani Nikula <jani.nikula@intel.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: add missing condition for committing planes on crtc
Date: Wed, 4 May 2016 17:30:47 +0300	[thread overview]
Message-ID: <20160504143047.GQ4329@intel.com> (raw)
In-Reply-To: <1462369234-27807-1-git-send-email-lionel.g.landwerlin@intel.com>

On Wed, May 04, 2016 at 02:40:34PM +0100, Lionel Landwerlin wrote:
> We are currently missing the color management update condition to
> commit planes on crtc.
> 
> v2: add comment about moving the commit of color management registers
>     to an async worker
> 
> v3: Commit color management register right after vblank
> 
> Fixes: 20a34e78f0d7 (drm/i915: Update color management during vblank evasion.)
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
> ---
>  drivers/gpu/drm/i915/intel_display.c | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 45c218d..c6acfe5 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -13688,6 +13688,11 @@ static int intel_atomic_commit(struct drm_device *dev,
>  
>  		if (dev_priv->display.optimize_watermarks)
>  			dev_priv->display.optimize_watermarks(intel_cstate);
> +
> +		if (crtc->state->color_mgmt_changed) {
> +			intel_color_set_csc(crtc->state);

As I said earlier, csc shouldn't be here, at least on pch
platforms. And someone should actually double check whether
vlv/chv have double buffered csc registers or not. Oh and
with these frankensocs the double buffering scheme used 
(if any) might be totally crazy, like it is for the pipe B
primary plane scaler on chv. A fact which the spec fails
to explain IIRC. So I'd recommend poking at the hardware
to figure out how it actually works.

> +			intel_color_load_luts(crtc->state);
> +		}
>  	}
>  
>  	for_each_crtc_in_state(state, crtc, old_crtc_state, i) {
> -- 
> 2.8.0.rc3.226.g39d4020

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

  reply	other threads:[~2016-05-04 14:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-04 13:40 [PATCH] drm/i915: add missing condition for committing planes on crtc Lionel Landwerlin
2016-05-04 14:30 ` Ville Syrjälä [this message]
2016-05-05 14:04   ` Lionel Landwerlin
2016-05-06 10:52     ` Ville Syrjälä
2016-05-09  7:41       ` Daniel Vetter
2016-05-04 16:22 ` ✓ Fi.CI.BAT: success for drm/i915: add missing condition for committing planes on crtc (rev3) Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2016-05-25 13:30 [PATCH] drm/i915: add missing condition for committing planes on crtc Lionel Landwerlin
2016-05-25 13:20 Lionel Landwerlin
2016-05-09 14:40 Lionel Landwerlin
2016-05-11 10:51 ` Maarten Lankhorst
2016-05-12 10:31   ` Lionel Landwerlin
2016-05-17  7:28     ` Daniel Vetter
2016-05-04 11:13 Lionel Landwerlin
2016-05-09  7:37 ` Daniel Vetter
2016-04-08 16:30 Lionel Landwerlin
2016-04-18 11:05 ` Lionel Landwerlin
2016-04-21 13:30   ` Maarten Lankhorst
2016-04-21 13:57     ` Ville Syrjälä
2016-05-04 10:25       ` Lionel Landwerlin
2016-05-04 10:30         ` Maarten Lankhorst
2016-05-04 11:41         ` Ville Syrjälä
2016-04-18 11:06 ` Maarten Lankhorst
2016-04-18 11:28 ` Ville Syrjälä

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=20160504143047.GQ4329@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=lionel.g.landwerlin@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.