All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: ville.syrjala@linux.intel.com, dri-devel@lists.freedesktop.org
Subject: Re: [RFC][PATCH 4/4] drm: i915: Atomic pageflip WIP
Date: Fri, 14 Sep 2012 14:57:26 +0100	[thread overview]
Message-ID: <84c8a8$5o3vcu@orsmga001.jf.intel.com> (raw)
In-Reply-To: <1347464827-14187-5-git-send-email-ville.syrjala@linux.intel.com>

On Wed, 12 Sep 2012 18:47:07 +0300, ville.syrjala@linux.intel.com wrote:
> +static void intel_flip_finish(struct drm_flip *flip)
> +{
> +	struct intel_flip *intel_flip =
> +		container_of(flip, struct intel_flip, base);
> +	struct drm_device *dev = intel_flip->crtc->dev;
> +
> +	if (intel_flip->old_bo) {
> +		mutex_lock(&dev->struct_mutex);
> +
> +		intel_finish_fb(intel_flip->old_bo);

So if I understand correctly, this code is called after the flip is
already complete?

The intel_finish_fb() exists to flush pending batches and flips on the
current fb, prior to changing the scanout registers. (There is a
hardware dependency such that the GPU may be executing a command that
required the current modesetting.) In the case of flip completion, all
of those dependencies have already been retired and so the finish should
be a no-op. And so it should no be required, nor the changes to
intel_finish_fb (which should have included a change in the name to
indicate that is now taking the fb_obj).

> +		intel_unpin_fb_obj(intel_flip->old_bo);
> +
> +		mutex_unlock(&dev->struct_mutex);
> +	}
> +
> +}
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2012-09-14 13:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12 15:47 [RFC][PATCH] Atomic page flip WIP ville.syrjala
2012-09-12 15:47 ` [RFC][PATCH 1/4] drm/i915: Try to commit single pipe in one go ville.syrjala
2012-09-12 15:47 ` [RFC][PATCH 2/4] drm: Add drm_flip helper ville.syrjala
2012-09-12 15:47 ` [RFC][PATCH 3/4] drm: i915: Pass gem object to intel_finish_fb() ville.syrjala
2012-09-12 15:47 ` [RFC][PATCH 4/4] drm: i915: Atomic pageflip WIP ville.syrjala
2012-09-14 13:57   ` Chris Wilson [this message]
2012-09-14 14:21     ` Ville Syrjälä
2012-09-14 14:27       ` Chris Wilson
2012-09-14 15:30         ` Ville Syrjälä
2012-09-14 15:39           ` Daniel Vetter
2012-09-14 15:52             ` Ville Syrjälä
2012-09-14 15:56           ` Chris Wilson
2012-09-14 16:07             ` 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='84c8a8$5o3vcu@orsmga001.jf.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ville.syrjala@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 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.