From: Ander Conselvan de Oliveira <conselvan2@gmail.com>
To: Matt Roper <matthew.d.roper@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 07/10] drm/i915: Consolidate plane 'cleanup' operations (v2)
Date: Tue, 02 Dec 2014 16:10:03 +0200 [thread overview]
Message-ID: <547DC83B.6050105@gmail.com> (raw)
In-Reply-To: <1417477218-9519-7-git-send-email-matthew.d.roper@intel.com>
On 12/02/2014 01:40 AM, Matt Roper wrote:
> All plane update functions need to unpin the old framebuffer when
> flipping to a new one. Pull this logic into a separate function to ease
> the integration with atomic plane helpers.
>
> v2: Don't wait for vblank if we don't have an old fb to cleanup (Ander)
>
> Signed-off-by: Matt Roper <matthew.d.roper@intel.com>
> ---
> drivers/gpu/drm/i915/intel_display.c | 59 ++++++++++++++++++++++++------------
> drivers/gpu/drm/i915/intel_drv.h | 2 ++
> drivers/gpu/drm/i915/intel_sprite.c | 27 ++++++-----------
> 3 files changed, 51 insertions(+), 37 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index f48faaa..98e4fbf 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
[...]
> @@ -12120,6 +12134,13 @@ intel_cursor_plane_update(struct drm_plane *plane, struct drm_crtc *crtc,
>
> intel_commit_cursor_plane(plane, &state);
>
> + if (fb != old_fb) {
> + if (intel_crtc->active)
> + intel_wait_for_vblank(dev, intel_crtc->pipe);
> + if (old_fb)
> + intel_cleanup_plane_fb(plane, old_fb);
> + }
> +
> return 0;
> }
>
We're still waiting for vblank when obj is NULL here.
[...]
> diff --git a/drivers/gpu/drm/i915/intel_sprite.c b/drivers/gpu/drm/i915/intel_sprite.c
> index 5d8c2e0..152a32d 100644
> --- a/drivers/gpu/drm/i915/intel_sprite.c
> +++ b/drivers/gpu/drm/i915/intel_sprite.c
[...]
> @@ -1390,6 +1373,14 @@ intel_update_plane(struct drm_plane *plane, struct drm_crtc *crtc,
> }
>
> intel_commit_sprite_plane(plane, &state);
> +
> + if (fb != old_fb) {
> + if (intel_crtc->active)
> + intel_wait_for_vblank(dev, intel_crtc->pipe);
> + if (old_fb)
> + intel_cleanup_plane_fb(plane, old_fb);
> + }
> +
And also here.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-12-02 14:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 23:40 [PATCH 01/10] drm: add helper to get crtc timings (v5) Matt Roper
2014-12-01 23:40 ` [PATCH 02/10] drm/i915: remove intel_crtc_cursor_set_obj() (v5) Matt Roper
2014-12-01 23:40 ` [PATCH 03/10] drm/i915: remove intel_pipe_set_base() (v4) Matt Roper
2014-12-01 23:40 ` [PATCH 04/10] drm/i915: Introduce intel_prepare_cursor_plane() (v2) Matt Roper
2014-12-01 23:40 ` [PATCH 05/10] drm/i915: Make intel_plane_state subclass drm_plane_state Matt Roper
2014-12-01 23:40 ` [PATCH 06/10] drm/i915: Consolidate plane 'prepare' functions (v2) Matt Roper
2014-12-01 23:40 ` [PATCH 07/10] drm/i915: Consolidate plane 'cleanup' operations (v2) Matt Roper
2014-12-02 14:10 ` Ander Conselvan de Oliveira [this message]
2014-12-02 15:45 ` [PATCH 7/7] drm/i915: Consolidate plane 'cleanup' operations (v3) Matt Roper
2014-12-03 9:52 ` Ander Conselvan de Oliveira
2014-12-01 23:40 ` [PATCH 08/10] drm/i915: Consolidate top-level .update_plane() handlers Matt Roper
2014-12-01 23:40 ` [PATCH 09/10] drm/i915: Ensure state->crtc is non-NULL for plane updates Matt Roper
2014-12-01 23:40 ` [PATCH 10/10] drm/i915: Make all plane disables use 'update_plane' (v2) Matt Roper
2014-12-02 15:14 ` Ander Conselvan de Oliveira
2014-12-02 15:59 ` [PATCH 10/10] drm/i915: Make all plane disables use 'update_plane' (v3) Matt Roper
2014-12-02 16:26 ` [PATCH 10/10] drm/i915: Make all plane disables use 'update_plane' (v4) Matt Roper
2014-12-03 9:53 ` Ander Conselvan de Oliveira
2014-12-04 18:27 ` [PATCH 10/10] drm/i915: Make all plane disables use 'update_plane' (v5) Matt Roper
2014-12-05 8:15 ` Ander Conselvan de Oliveira
2014-12-05 20:31 ` 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=547DC83B.6050105@gmail.com \
--to=conselvan2@gmail.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.d.roper@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