From: Imre Deak <imre.deak@intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: paper over a pipe-enable vs pageflip race
Date: Mon, 08 Oct 2012 20:19:20 +0300 [thread overview]
Message-ID: <1349716760.21394.1.camel@ideak-mobl> (raw)
In-Reply-To: <1349371203-15130-1-git-send-email-daniel.vetter@ffwll.ch>
On Thu, 2012-10-04 at 19:20 +0200, Daniel Vetter wrote:
> I've discovered this on my ivb machine while stress-testing the new
> flip_tests. Only harmful effect observed is that the timestamp is a
> bit bogus.
>
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
I've seen the same issue on an ivb ultrabook machine and the patch gets
rid of it, so:
Tested-by: Imre Deak <imre.deak@intel.com>
> ---
> drivers/gpu/drm/i915/intel_display.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 67912fe..9cecfd7 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -3253,6 +3253,16 @@ static void ironlake_crtc_enable(struct drm_crtc *crtc)
>
> if (HAS_PCH_CPT(dev))
> intel_cpt_verify_modeset(dev, intel_crtc->pipe);
> +
> + /*
> + * There seems to be a race in PCH platform hw (at least on some
> + * outputs) where an enabled pipe still completes any pageflip right
> + * away (as if the pipe is off) instead of waiting for vblank. As soon
> + * as the first vblank happend, everything works as expected. Hence just
> + * wait for one vblank before returning to avoid strange things
> + * happening.
> + */
> + intel_wait_for_vblank(dev, intel_crtc->pipe);
> }
>
> static void ironlake_crtc_disable(struct drm_crtc *crtc)
next prev parent reply other threads:[~2012-10-08 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-04 17:20 [PATCH] drm/i915: paper over a pipe-enable vs pageflip race Daniel Vetter
2012-10-08 17:19 ` Imre Deak [this message]
2012-10-08 17:32 ` Daniel Vetter
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=1349716760.21394.1.camel@ideak-mobl \
--to=imre.deak@intel.com \
--cc=daniel.vetter@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