From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: Move updating color management to before vblank evasion
Date: Wed, 1 Mar 2017 17:38:50 +0200 [thread overview]
Message-ID: <20170301153850.GX31595@intel.com> (raw)
In-Reply-To: <20170228150125.GM31595@intel.com>
On Tue, Feb 28, 2017 at 05:01:25PM +0200, Ville Syrjälä wrote:
> On Tue, Feb 28, 2017 at 03:28:47PM +0100, Maarten Lankhorst wrote:
> > This cannot be done reliably during vblank evasasion
> > since the color management registers are not double buffered.
> >
> > The original commit that moved it always during vblank evasion was
> > wrong, so revert it to before vblank evasion again.
> >
> > Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> > Fixes: 20a34e78f0d7 ("drm/i915: Update color management during vblank evasion.")
> > Cc: stable@vger.kernel.org # v4.7+
>
> Wasn't there a bugzilla + tested-by ?
Seems we have two bugzillas now:
https://bugs.freedesktop.org/show_bug.cgi?id=91883
https://bugs.freedesktop.org/show_bug.cgi?id=99991
First one is about the atomic update fails, the second about
the assert_dsi_pll() mutex vs. irq_disabled() warning.
No actual t-bs for this specific variant of the patch (yet)
from what I can see.
Anyways, this is
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> > ---
> > drivers/gpu/drm/i915/intel_display.c | 12 +++++++-----
> > 1 file changed, 7 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> > index 3c862d0ab389..a0108041fd4a 100644
> > --- a/drivers/gpu/drm/i915/intel_display.c
> > +++ b/drivers/gpu/drm/i915/intel_display.c
> > @@ -13301,17 +13301,19 @@ static void intel_begin_crtc_commit(struct drm_crtc *crtc,
> > to_intel_atomic_state(old_crtc_state->state);
> > bool modeset = needs_modeset(crtc->state);
> >
> > + if (!modeset &&
> > + (intel_cstate->base.color_mgmt_changed ||
> > + intel_cstate->update_pipe)) {
> > + intel_color_set_csc(crtc->state);
> > + intel_color_load_luts(crtc->state);
> > + }
> > +
> > /* Perform vblank evasion around commit operation */
> > intel_pipe_update_start(intel_crtc);
> >
> > if (modeset)
> > goto out;
> >
> > - if (crtc->state->color_mgmt_changed || to_intel_crtc_state(crtc->state)->update_pipe) {
> > - intel_color_set_csc(crtc->state);
> > - intel_color_load_luts(crtc->state);
> > - }
> > -
> > if (intel_cstate->update_pipe)
> > intel_update_pipe_config(intel_crtc, old_intel_cstate);
> > else if (INTEL_GEN(dev_priv) >= 9)
> > --
> > 2.7.4
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> --
> Ville Syrjälä
> Intel OTC
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-03-01 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 14:28 [PATCH 1/2] drm/i915: Move updating color management to before vblank evasion Maarten Lankhorst
2017-02-28 14:28 ` [PATCH 2/2] drm/i915: Complain if we take too long under " Maarten Lankhorst
2017-03-01 15:40 ` Ville Syrjälä
2017-03-06 12:06 ` Maarten Lankhorst
2017-02-28 15:01 ` [PATCH 1/2] drm/i915: Move updating color management to before " Ville Syrjälä
2017-03-01 15:38 ` Ville Syrjälä [this message]
2017-02-28 18:53 ` ✓ Fi.CI.BAT: success for series starting with [1/2] " Patchwork
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=20170301153850.GX31595@intel.com \
--to=ville.syrjala@linux.intel.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