From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Gustavo Padovan <gustavo@padovan.org>
Cc: intel-gfx@lists.freedesktop.org,
Gustavo Padovan <gustavo.padovan@collabora.co.uk>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH -v4 0/4] split plane's updates functions into check() and commit()
Date: Mon, 8 Sep 2014 16:59:42 +0300 [thread overview]
Message-ID: <20140908135942.GY4193@intel.com> (raw)
In-Reply-To: <1409947489-2667-1-git-send-email-gustavo@padovan.org>
On Fri, Sep 05, 2014 at 05:04:45PM -0300, Gustavo Padovan wrote:
> From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
>
> This is the beginning of the work to prepare i915 for the upcoming
> atomic modesetting API. Here we split the plane update fucntions in
> the check and commit states.
>
> v2: use struct intel_plane_state to keep states between check and
> commit stages.
>
> v3: take Ville's comments:
> - rename pstate to state
> - get rid of non-drm_rect coordinates in intel_plane_state
> - keep 'clip' const
>
> v4: take more Ville's comments:
> - populates orig_dst and orig_src too
> - use orig_dst coordinates to program the cursor plane
>
> Gustavo Padovan (4):
> drm/i915: create struct intel_plane_state
> drm/i915: split intel_update_plane into check() and commit()
> drm/i915: split intel_cursor_plane_update() into check() and commit()
> drm/i915: split intel_primary_plane_setplane() into check() and
> commit()
It's looking pretty nice. I didn't spot any more problems, so for the
series:
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> drivers/gpu/drm/i915/intel_display.c | 240 +++++++++++++++++++++--------------
> drivers/gpu/drm/i915/intel_drv.h | 12 ++
> drivers/gpu/drm/i915/intel_sprite.c | 233 ++++++++++++++++++++--------------
> 3 files changed, 298 insertions(+), 187 deletions(-)
>
> --
> 1.9.3
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2014-09-08 13:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 20:04 [PATCH -v4 0/4] split plane's updates functions into check() and commit() Gustavo Padovan
2014-09-05 20:04 ` [PATCH -v4 1/4] drm/i915: create struct intel_plane_state Gustavo Padovan
2014-09-05 20:04 ` [PATCH -v4 2/4] drm/i915: split intel_update_plane into check() and commit() Gustavo Padovan
2014-09-11 16:42 ` [Intel-gfx] " Jani Nikula
2014-09-11 20:42 ` [PATCH] drm/i915: Fix regression in the sprite plane update split Gustavo Padovan
2014-09-12 7:12 ` Jani Nikula
2014-09-12 8:27 ` Daniel Vetter
2014-09-05 20:04 ` [PATCH -v4 3/4] drm/i915: split intel_cursor_plane_update() into check() and commit() Gustavo Padovan
2014-09-05 20:22 ` [PATCH -v5 " Gustavo Padovan
2014-09-05 20:04 ` [PATCH -v4 4/4] drm/i915: split intel_primary_plane_setplane() " Gustavo Padovan
2014-09-08 13:53 ` [Intel-gfx] [PATCH -v4 0/4] split plane's updates functions " Ville Syrjälä
2014-09-08 13:59 ` Ville Syrjälä [this message]
2014-09-08 16: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=20140908135942.GY4193@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo.padovan@collabora.co.uk \
--cc=gustavo@padovan.org \
--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