From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Arthur Grillo <arthurgrillo@riseup.net>
Cc: carlos.craveiro@usp.br, tales.aparecida@gmail.com,
dlatypov@google.com, javierm@redhat.com,
dri-devel@lists.freedesktop.org, mairacanal@riseup.net,
maxime@cerno.tech, andrealmeid@riseup.net, airled@gmail.com,
matheus.vieira.g@usp.br
Subject: Re: [PATCH 1/5] drm/tests: Test drm_rect_intersect()
Date: Wed, 22 Mar 2023 16:26:52 +0200 [thread overview]
Message-ID: <ZBsQLEdrJYnNUDPo@intel.com> (raw)
In-Reply-To: <20230322140701.69852-2-arthurgrillo@riseup.net>
On Wed, Mar 22, 2023 at 11:06:57AM -0300, Arthur Grillo wrote:
> Insert test for the drm_rect_intersect() function, it also create a
> helper for comparing drm_rects more easily.
>
> Signed-off-by: Arthur Grillo <arthurgrillo@riseup.net>
> ---
> drivers/gpu/drm/tests/drm_rect_test.c | 30 +++++++++++++++++++++++++++
> 1 file changed, 30 insertions(+)
>
> diff --git a/drivers/gpu/drm/tests/drm_rect_test.c b/drivers/gpu/drm/tests/drm_rect_test.c
> index e9809ea32696..f700984f70a8 100644
> --- a/drivers/gpu/drm/tests/drm_rect_test.c
> +++ b/drivers/gpu/drm/tests/drm_rect_test.c
> @@ -9,6 +9,15 @@
>
> #include <drm/drm_rect.h>
>
> +static void drm_rect_compare(struct kunit *test, const struct drm_rect *r,
> + const struct drm_rect *expected)
> +{
> + KUNIT_EXPECT_EQ(test, r->x1, expected->x1);
> + KUNIT_EXPECT_EQ(test, r->y1, expected->y1);
> + KUNIT_EXPECT_EQ(test, drm_rect_width(r), drm_rect_width(expected));
> + KUNIT_EXPECT_EQ(test, drm_rect_height(r), drm_rect_height(expected));
> +}
We already have a drm_rect_equals().
> +
> static void drm_test_rect_clip_scaled_div_by_zero(struct kunit *test)
> {
> struct drm_rect src, dst, clip;
> @@ -196,11 +205,32 @@ static void drm_test_rect_clip_scaled_signed_vs_unsigned(struct kunit *test)
> KUNIT_EXPECT_FALSE_MSG(test, drm_rect_visible(&src), "Source should not be visible\n");
> }
>
> +static void drm_test_rect_intersect(struct kunit *test)
> +{
> + struct drm_rect r1, r2;
> + bool visible;
> +
> + drm_rect_init(&r1, 0, 0, 2, 2);
> + drm_rect_init(&r2, 1, 1, 2, 2);
> +
> + visible = drm_rect_intersect(&r1, &r2);
> +
> + KUNIT_EXPECT_TRUE_MSG(test, visible, "Interserction should be a visible rect");
> + drm_rect_compare(test, &r1, &DRM_RECT_INIT(1, 1, 1, 1));
> +
> + drm_rect_init(&r1, 0, 0, 1, 1);
> +
I would re-init r2 here too to make it easier to see what we're
actually testing.
I would probably test a few more variations of the overlap between
the rectangles, eg: equal rectangles, one smaller one fully inside
the bigger one, overlaps across different edges/corners.
> + visible = drm_rect_intersect(&r1, &r2);
> +
> + KUNIT_EXPECT_FALSE_MSG(test, visible, "Interserction should not be a visible rect");
> +}
> +
> static struct kunit_case drm_rect_tests[] = {
> KUNIT_CASE(drm_test_rect_clip_scaled_div_by_zero),
> KUNIT_CASE(drm_test_rect_clip_scaled_not_clipped),
> KUNIT_CASE(drm_test_rect_clip_scaled_clipped),
> KUNIT_CASE(drm_test_rect_clip_scaled_signed_vs_unsigned),
> + KUNIT_CASE(drm_test_rect_intersect),
> { }
> };
>
> --
> 2.39.2
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2023-03-22 14:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 14:06 [PATCH 0/5] Create tests for the drm_rect functions Arthur Grillo
2023-03-22 14:06 ` [PATCH 1/5] drm/tests: Test drm_rect_intersect() Arthur Grillo
2023-03-22 14:26 ` Ville Syrjälä [this message]
2023-03-22 19:39 ` Arthur Grillo Queiroz Cabral
2023-03-22 14:06 ` [PATCH 2/5] drm/tests: Test drm_rect_calc_hscale() Arthur Grillo
2023-03-22 14:29 ` Ville Syrjälä
2023-03-22 14:06 ` [PATCH 3/5] drm/tests: Test drm_rect_calc_vscale() Arthur Grillo
2023-03-22 14:07 ` [PATCH 4/5] drm/tests: Test drm_rect_rotate() Arthur Grillo
2023-03-22 14:32 ` Ville Syrjälä
2023-03-22 14:07 ` [PATCH 5/5] drm/test: Test drm_rect_rotate_inv() Arthur Grillo
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=ZBsQLEdrJYnNUDPo@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=airled@gmail.com \
--cc=andrealmeid@riseup.net \
--cc=arthurgrillo@riseup.net \
--cc=carlos.craveiro@usp.br \
--cc=dlatypov@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=mairacanal@riseup.net \
--cc=matheus.vieira.g@usp.br \
--cc=maxime@cerno.tech \
--cc=tales.aparecida@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.