From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: ville.syrjala@linux.intel.com
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v4] drm: Add struct drm_rect and assorted utility functions
Date: Sat, 06 Apr 2013 02:00:31 +0200 [thread overview]
Message-ID: <1829021.moR8pyskht@avalon> (raw)
In-Reply-To: <1365167976-15451-1-git-send-email-ville.syrjala@linux.intel.com>
Hi Ville,
Thanks for the patch.
On Friday 05 April 2013 16:19:36 ville.syrjala@linux.intel.com wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> struct drm_rect represents a simple rectangle. The utility
> functions are there to help driver writers.
>
> v2: Moved the region stuff into its own file, made the smaller funcs
> static inline, used 64bit maths in the scaled clipping function to
> avoid overflows (instead it will saturate to INT_MIN or INT_MAX).
> v3: Renamed drm_region to drm_rect, drm_region_clip to
> drm_rect_intersect, and drm_region_subsample to drm_rect_downscale.
> v4: Renamed some function parameters, improve kernel-doc comments a bit,
> and actually generate documentation for drm_rect.[ch].
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> Documentation/DocBook/drm.tmpl | 2 +
> drivers/gpu/drm/Makefile | 3 +-
> drivers/gpu/drm/drm_rect.c | 96 ++++++++++++++++++++++++++++++
> include/drm/drm_rect.h | 132 ++++++++++++++++++++++++++++++++++++++
> 4 files changed, 232 insertions(+), 1 deletion(-)
> create mode 100644 drivers/gpu/drm/drm_rect.c
> create mode 100644 include/drm/drm_rect.h
[snip]
> diff --git a/drivers/gpu/drm/drm_rect.c b/drivers/gpu/drm/drm_rect.c
> new file mode 100644
> index 0000000..a9861bd
> --- /dev/null
> +++ b/drivers/gpu/drm/drm_rect.c
[snip]
> +/**
> + * drm_rect_clip_scaled - perform a scaled clip operation
> + * @src: source window rectangle
> + * @dst: destination window rectangle
> + * @clip: clip rectangle
> + * @hscale: horizontal scaling factor
> + * @vscale: vertical scaling factor
> + *
> + * Clip rectangle @dst by rectangle @clip. Clip rectangle @src by the
> + * same amounts multiplied by @hscale and @vscale.
> + *
> + * RETUTRNS:
s/RETUTRNS/RETURNS/
> + * %true if rectangle @dst is still visible after being clipped,
> + * %false otherwise
> + */
Otherwise,
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-04-06 0:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 15:46 [PATCH v3 1/4] drm: Add struct drm_rect and assorted utility functions ville.syrjala
2013-03-27 15:46 ` [PATCH v3 2/4] drm: Add drm_rect_calc_{hscale, vscale}() " ville.syrjala
2013-03-27 15:46 ` [PATCH v2 3/4] drm: Add drm_rect_debug_print() ville.syrjala
2013-03-27 15:46 ` [PATCH v3 4/4] drm/i915: Implement proper clipping for video sprites ville.syrjala
2013-04-04 16:38 ` [PATCH v3 1/4] drm: Add struct drm_rect and assorted utility functions Laurent Pinchart
2013-04-04 19:52 ` Ville Syrjälä
2013-04-04 23:51 ` Laurent Pinchart
2013-04-05 13:13 ` Ville Syrjälä
2013-04-05 13:19 ` [PATCH v4] " ville.syrjala
2013-04-06 0:00 ` Laurent Pinchart [this message]
2013-04-08 11:11 ` 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=1829021.moR8pyskht@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox