From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: add missing condition for committing planes on crtc
Date: Thu, 12 May 2016 11:31:16 +0100 [thread overview]
Message-ID: <57345B74.7040404@intel.com> (raw)
In-Reply-To: <374a8cf2-6ba8-a8c6-22d4-cb28d9196bae@linux.intel.com>
Hey Daniel,
Sorry to nag again. Could you cherry pick this?
Thanks!
-
Lionel
On 11/05/16 11:51, Maarten Lankhorst wrote:
> Op 09-05-16 om 16:40 schreef Lionel Landwerlin:
>> 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
>>
>> v4: Move back color management commit condition together with planes
>> commit
>>
>> Fixes: 20a34e78f0d7 (drm/i915: Update color management during vblank evasion.)
>> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>> 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 | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
>> index 3c6b7b9..b63f33d 100644
>> --- a/drivers/gpu/drm/i915/intel_display.c
>> +++ b/drivers/gpu/drm/i915/intel_display.c
>> @@ -13669,7 +13669,9 @@ static int intel_atomic_commit(struct drm_device *dev,
>> intel_fbc_enable(intel_crtc);
>>
>> if (crtc->state->active &&
>> - (crtc->state->planes_changed || update_pipe))
>> + (crtc->state->planes_changed ||
>> + crtc->state->color_mgmt_changed ||
>> + update_pipe))
>> drm_atomic_helper_commit_planes_on_crtc(old_crtc_state);
>>
>> if (pipe_config->base.active && needs_vblank_wait(pipe_config))
> Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-05-12 10:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 14:40 [PATCH] drm/i915: add missing condition for committing planes on crtc Lionel Landwerlin
2016-05-11 10:51 ` Maarten Lankhorst
2016-05-12 10:31 ` Lionel Landwerlin [this message]
2016-05-17 7:28 ` Daniel Vetter
-- strict thread matches above, loose matches on Subject: below --
2016-05-25 13:30 Lionel Landwerlin
2016-05-25 13:20 Lionel Landwerlin
2016-05-04 13:40 Lionel Landwerlin
2016-05-04 14:30 ` Ville Syrjälä
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 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=57345B74.7040404@intel.com \
--to=lionel.g.landwerlin@intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
/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