From: Lionel Landwerlin <llandwerlin@gmail.com>
To: intel-gfx@lists.freedesktop.org,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: Re: [PATCH 3/3] drm/i915: Update color management during vblank evasion.
Date: Thu, 31 Mar 2016 11:35:20 +0100 [thread overview]
Message-ID: <56FCFD68.30708@gmail.com> (raw)
In-Reply-To: <56FC01CB.9070809@intel.com>
On 30/03/16 17:41, Lionel Landwerlin wrote:
> On 30/03/16 16:16, Maarten Lankhorst wrote:
>> Without this a vblank may occur between updating color management
>> and planes, which should be prevented.
>>
>> intel_color_set_csc was called in update pipe config because the
>> handover from hardware may not have any csc set, which resulted
>> in a black screen. Because of this also update color management
>> during fastset.
>>
>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Tested-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
Reviewed-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
>
>> ---
>> drivers/gpu/drm/i915/intel_display.c | 25 ++++++++++---------------
>> 1 file changed, 10 insertions(+), 15 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_display.c
>> b/drivers/gpu/drm/i915/intel_display.c
>> index 4f913e5febf1..179461b45ce3 100644
>> --- a/drivers/gpu/drm/i915/intel_display.c
>> +++ b/drivers/gpu/drm/i915/intel_display.c
>> @@ -3222,9 +3222,6 @@ static void intel_update_pipe_config(struct
>> intel_crtc *crtc,
>> old_crtc_state->pipe_src_w, old_crtc_state->pipe_src_h,
>> pipe_config->pipe_src_w, pipe_config->pipe_src_h);
>> - if (HAS_DDI(dev))
>> - intel_color_set_csc(&pipe_config->base);
>> -
>> /*
>> * Update pipe size and adjust fitter if needed: the reason for
>> this is
>> * that in compute_mode_changes we check the native mode (not
>> the pfit
>> @@ -13603,18 +13600,6 @@ static int intel_atomic_commit(struct
>> drm_device *dev,
>> dev_priv->display.crtc_enable(crtc);
>> }
>> - if (!modeset &&
>> - crtc->state->active &&
>> - crtc->state->color_mgmt_changed) {
>> - /*
>> - * Only update color management when not doing
>> - * a modeset as this will be done by
>> - * crtc_enable already.
>> - */
>> - intel_color_set_csc(crtc->state);
>> - intel_color_load_luts(crtc->state);
>> - }
>> -
>> if (!modeset)
>> intel_pre_plane_update(to_intel_crtc_state(old_crtc_state));
>> @@ -13933,6 +13918,16 @@ static void intel_begin_crtc_commit(struct
>> drm_crtc *crtc,
>> if (modeset)
>> return;
>> + if (crtc->state->color_mgmt_changed ||
>> to_intel_crtc_state(crtc->state)->update_pipe) {
>> + /*
>> + * Only update color management when not doing
>> + * a modeset as this will be done by
>> + * crtc_enable already.
>> + */
> I guess we can drop this comment.
>> + intel_color_set_csc(crtc->state);
>> + intel_color_load_luts(crtc->state);
>> + }
>> +
>> if (to_intel_crtc_state(crtc->state)->update_pipe)
>> intel_update_pipe_config(intel_crtc, old_intel_state);
>> else if (INTEL_INFO(dev)->gen >= 9)
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-03-31 10:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 15:16 [PATCH 0/3] drm/i915: color management atomic fixes Maarten Lankhorst
2016-03-30 15:16 ` [PATCH 1/3] drm/i915: Pass crtc_state to color management functions Maarten Lankhorst
2016-03-30 16:44 ` Lionel Landwerlin
2016-03-30 15:16 ` [PATCH 2/3] drm/i915: Do not check crtc_state->active in intel_color_load_luts Maarten Lankhorst
2016-03-30 16:42 ` Lionel Landwerlin
2016-03-30 15:16 ` [PATCH 3/3] drm/i915: Update color management during vblank evasion Maarten Lankhorst
2016-03-30 16:41 ` Lionel Landwerlin
2016-03-31 10:35 ` Lionel Landwerlin [this message]
2016-03-31 10:35 ` Lionel Landwerlin
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=56FCFD68.30708@gmail.com \
--to=llandwerlin@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@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