dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Eduardo Gallo Filho <gcarlos@disroot.org>
To: dri-devel@lists.freedesktop.org
Cc: andrealmeid@igalia.com, tzimmermann@suse.de,
	tales.aparecida@gmail.com, mripard@kernel.org,
	mairacanal@riseup.net,
	Carlos Eduardo Gallo Filho <gcarlos@disroot.org>,
	davidgow@google.com, michal.winiarski@intel.com,
	arthurgrillo@riseup.net
Subject: [PATCH v2 4/4] drm/tests: Add test case for drm_internal_framebuffer_create()
Date: Tue, 18 Jul 2023 15:17:26 -0300	[thread overview]
Message-ID: <20230718181726.3799-5-gcarlos@disroot.org> (raw)
In-Reply-To: <20230718181726.3799-1-gcarlos@disroot.org>

Introduce a test to cover the creation of framebuffer with
modifier on a device that don't support it.

Signed-off-by: Carlos Eduardo Gallo Filho <gcarlos@disroot.org>
---
 drivers/gpu/drm/tests/drm_framebuffer_test.c | 29 ++++++++++++++++++++
 1 file changed, 29 insertions(+)

diff --git a/drivers/gpu/drm/tests/drm_framebuffer_test.c b/drivers/gpu/drm/tests/drm_framebuffer_test.c
index cbab12503f5f..0f1744b5d2c1 100644
--- a/drivers/gpu/drm/tests/drm_framebuffer_test.c
+++ b/drivers/gpu/drm/tests/drm_framebuffer_test.c
@@ -388,6 +388,34 @@ static void drm_framebuffer_test_to_desc(const struct drm_framebuffer_test *t, c
 KUNIT_ARRAY_PARAM(drm_framebuffer_create, drm_framebuffer_create_cases,
 		  drm_framebuffer_test_to_desc);
 
+/*
+ * This test is very similar to drm_test_framebuffer_create, except that it
+ * set mock->mode_config.fb_modifiers_not_supported member to 1, covering
+ * the case of trying to create a framebuffer with modifiers without the
+ * device really supporting it.
+ */
+static void drm_test_framebuffer_modifiers_not_supported(struct kunit *test)
+{
+	/* A valid cmd with modifier */
+	struct drm_mode_fb_cmd2 cmd = {
+		.width = MAX_WIDTH, .height = MAX_HEIGHT,
+		.pixel_format = DRM_FORMAT_ABGR8888, .handles = { 1, 0, 0 },
+		.offsets = { UINT_MAX / 2, 0, 0 }, .pitches = { 4 * MAX_WIDTH, 0, 0 },
+		.flags = DRM_MODE_FB_MODIFIERS,
+	};
+	struct drm_device *mock = test->priv;
+	int buffer_created = 0;
+
+	mock->dev_private = &buffer_created;
+	mock->mode_config.fb_modifiers_not_supported = 1;
+
+	drm_internal_framebuffer_create(mock, &cmd, NULL);
+	KUNIT_EXPECT_EQ(test, 0, buffer_created);
+
+	/* Restore original value */
+	mock->mode_config.fb_modifiers_not_supported = 0;
+}
+
 /* Parameters for testing drm_framebuffer_check_src_coords function */
 struct check_src_coords_case {
 	const char *name; /* Description of the parameter case */
@@ -513,6 +541,7 @@ KUNIT_ARRAY_PARAM(check_src_coords, check_src_coords_cases,
 		  check_src_coords_test_to_desc);
 
 static struct kunit_case drm_framebuffer_tests[] = {
+	KUNIT_CASE(drm_test_framebuffer_modifiers_not_supported),
 	KUNIT_CASE_PARAM(drm_test_framebuffer_check_src_coords, check_src_coords_gen_params),
 	KUNIT_CASE_PARAM(drm_test_framebuffer_create, drm_framebuffer_create_gen_params),
 	{ }
-- 
2.41.0


      parent reply	other threads:[~2023-07-18 18:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 18:17 [PATCH v2 0/4] Add documentation and KUnit tests for functions on drm_framebuffer.c Carlos Eduardo Gallo Filho
2023-07-18 18:17 ` [PATCH v2 1/4] drm: Add kernel-doc for drm_framebuffer_check_src_coords() Carlos Eduardo Gallo Filho
2023-07-19  7:24   ` Maxime Ripard
2023-07-18 18:17 ` [PATCH v2 2/4] drm/tests: Add test " Carlos Eduardo Gallo Filho
2023-07-19  6:50   ` kernel test robot
2023-07-19  7:36     ` Maxime Ripard
2023-07-19  7:49   ` Maxime Ripard
2023-07-19 16:24     ` Carlos
2023-07-19 14:33   ` kernel test robot
2023-07-18 18:17 ` [PATCH v2 3/4] drm/tests: Add parameters to the drm_test_framebuffer_create test Carlos Eduardo Gallo Filho
2023-07-18 18:17 ` Carlos Eduardo Gallo Filho [this message]

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=20230718181726.3799-5-gcarlos@disroot.org \
    --to=gcarlos@disroot.org \
    --cc=andrealmeid@igalia.com \
    --cc=arthurgrillo@riseup.net \
    --cc=davidgow@google.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=mairacanal@riseup.net \
    --cc=michal.winiarski@intel.com \
    --cc=mripard@kernel.org \
    --cc=tales.aparecida@gmail.com \
    --cc=tzimmermann@suse.de \
    /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