public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
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 -v2 3/4] drm/i915: create struct intel_plane_state
Date: Wed, 3 Sep 2014 11:22:15 +0300	[thread overview]
Message-ID: <20140903082215.GQ4193@intel.com> (raw)
In-Reply-To: <1409685827-29067-3-git-send-email-gustavo@padovan.org>

On Tue, Sep 02, 2014 at 04:23:46PM -0300, Gustavo Padovan wrote:
> From: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> 
> This new struct will be the storage of src and dst coordinates
> between the check and commit stages of a plane update.
> 
> Signed-off-by: Gustavo Padovan <gustavo.padovan@collabora.co.uk>
> ---
>  drivers/gpu/drm/i915/intel_drv.h | 20 ++++++++++++++++++++
>  1 file changed, 20 insertions(+)
> 
> diff --git a/drivers/gpu/drm/i915/intel_drv.h b/drivers/gpu/drm/i915/intel_drv.h
> index 4ab0d92..59c1675 100644
> --- a/drivers/gpu/drm/i915/intel_drv.h
> +++ b/drivers/gpu/drm/i915/intel_drv.h
> @@ -33,6 +33,7 @@
>  #include <drm/drm_crtc_helper.h>
>  #include <drm/drm_fb_helper.h>
>  #include <drm/drm_dp_mst_helper.h>
> +#include <drm/drm_rect.h>
>  
>  /**
>   * _wait_for - magic (register) wait macro
> @@ -227,6 +228,25 @@ typedef struct dpll {
>  	int	p;
>  } intel_clock_t;
>  
> +struct intel_plane_state {
> +	struct drm_crtc *crtc;
> +	struct drm_framebuffer *fb;
> +	int crtc_x;
> +	int crtc_y;
> +	unsigned int crtc_w;
> +	unsigned int crtc_h;
> +	uint32_t src_x;
> +	uint32_t src_y;
> +	uint32_t src_w;
> +	uint32_t src_h;

Seems to me we shouldn't need these non-drm_rect coordinates in
this struct. I'll comment a bit more on the next patch since that's
where this is used.

> +	struct drm_rect src;
> +	struct drm_rect dst;
> +	struct drm_rect clip;
> +	struct drm_rect orig_src;
> +	struct drm_rect orig_dst;
> +	bool visible;
> +};
> +
>  struct intel_plane_config {
>  	bool tiled;
>  	int size;
> -- 
> 1.9.3
> 
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2014-09-03  8:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 19:23 [PATCH -v2 1/4] drm/i915: init sprites with univeral plane init function Gustavo Padovan
2014-09-02 19:23 ` [PATCH -v2 2/4] drm/i915: trivial: remove unneed set to NULL Gustavo Padovan
2014-09-02 19:23 ` [PATCH -v2 3/4] drm/i915: create struct intel_plane_state Gustavo Padovan
2014-09-03  8:22   ` Ville Syrjälä [this message]
2014-09-02 19:23 ` [PATCH -v2 4/4] drm/i915: split intel_update_plane into check() and commit() Gustavo Padovan
2014-09-03  8:41   ` Ville Syrjälä
2014-09-03  8:18 ` [PATCH -v2 1/4] drm/i915: init sprites with univeral plane init function Ville Syrjälä
2014-09-03  8:36   ` Daniel Vetter
2014-09-03  8:38   ` Daniel Vetter
2014-09-03 10:36     ` Daniel Vetter
2014-09-03 13:38       ` [PATCH] " Gustavo Padovan
2014-09-03 13:44         ` 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=20140903082215.GQ4193@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