From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: Maxime Ripard <maxime.ripard@bootlin.com>,
David Airlie <airlied@linux.ie>, Sean Paul <sean@poorly.run>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/plane: Clarify our expectations for src/dst rectangles
Date: Thu, 10 Oct 2019 15:36:24 +0300 [thread overview]
Message-ID: <20191010123624.GD1208@intel.com> (raw)
In-Reply-To: <20191010112918.15724-1-maarten.lankhorst@linux.intel.com>
On Thu, Oct 10, 2019 at 01:29:17PM +0200, Maarten Lankhorst wrote:
> The rectangles are usually clipped, but it can be useful to have
> them unclipped, for example for cursor planes.
>
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> ---
> include/drm/drm_plane.h | 22 ++++++++++++++++++++--
> 1 file changed, 20 insertions(+), 2 deletions(-)
>
> diff --git a/include/drm/drm_plane.h b/include/drm/drm_plane.h
> index cd5903ad33f7..94bbbf215100 100644
> --- a/include/drm/drm_plane.h
> +++ b/include/drm/drm_plane.h
> @@ -183,8 +183,26 @@ struct drm_plane_state {
> */
> struct drm_property_blob *fb_damage_clips;
>
> - /** @src: clipped source coordinates of the plane (in 16.16) */
> - /** @dst: clipped destination coordinates of the plane */
> + /**
> + * @src:
> + *
> + * source coordinates of the plane (in 16.16).
> + *
> + * When using drm_atomic_helper_check_plane_state(),
> + * the coordinates are clipped, but the driver may choose
> + * to use unclipped coordinates instead.
> + *
> + * This can be useful when using a hardcoded size in a cursor plane.
I would instead say something like "when the hardware performs
the clipping automagically".
> + */
> + /**
> + * @dst:
> + *
> + * When using drm_atomic_helper_check_plane_state(),
> + * the coordinates are clipped, but the driver may choose
> + * to use unclipped coordinates instead.
> + *
> + * This can be useful when using a hardcoded size in a cursor plane.
> + */
> struct drm_rect src, dst;
>
> /**
> --
> 2.23.0
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Ville Syrjälä
Intel
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-10-10 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 11:29 [PATCH] drm/plane: Clarify our expectations for src/dst rectangles Maarten Lankhorst
2019-10-10 12:36 ` Ville Syrjälä [this message]
2019-10-10 12:46 ` Maarten Lankhorst
2019-10-10 13:07 ` Ville Syrjälä
2019-10-10 13:49 ` Maarten Lankhorst
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=20191010123624.GD1208@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maxime.ripard@bootlin.com \
--cc=sean@poorly.run \
/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