From: "André Almeida" <andrealmeid@igalia.com>
To: igt-dev@lists.freedesktop.org, Jeevan B <jeevan.b@intel.com>,
Kamil Konieczny <kamil.konieczny@linux.intel.com>
Cc: kernel-dev@igalia.com, "Vitaly Prosyak" <vitaly.prosyak@amd.com>,
"Alex Hung" <alex.hung@amd.com>, "Melissa Wen" <mwen@igalia.com>,
"Rodrigo Siqueira" <siqueira@igalia.com>,
"André Almeida" <andrealmeid@igalia.com>
Subject: [PATCH v4 1/3] tests/kms_async_flips: Check for atomic async flip cap
Date: Thu, 27 Mar 2025 19:15:59 -0300 [thread overview]
Message-ID: <20250327221601.19086-2-andrealmeid@igalia.com> (raw)
In-Reply-To: <20250327221601.19086-1-andrealmeid@igalia.com>
If a driver doesn't support doing an async flip through the atomic uAPI,
the atomic tests fails. Instead of failing, create a function that
checks for this capability and skip the test if is unsupported.
Signed-off-by: André Almeida <andrealmeid@igalia.com>
---
tests/kms_async_flips.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/tests/kms_async_flips.c b/tests/kms_async_flips.c
index da426f753..2975925c2 100644
--- a/tests/kms_async_flips.c
+++ b/tests/kms_async_flips.c
@@ -207,6 +207,12 @@ static void require_monotonic_timestamp(int fd)
"Monotonic timestamps not supported\n");
}
+static void require_atomic_async_cap(data_t *data)
+{
+ igt_require_f(igt_has_drm_cap(data->drm_fd, DRM_CAP_ATOMIC_ASYNC_PAGE_FLIP),
+ "Skipping, atomic flip async flip not supported");
+}
+
static void test_init(data_t *data)
{
drmModeModeInfo *mode;
@@ -687,6 +693,9 @@ static void run_test(data_t *data, void (*test)(data_t *))
{
igt_display_t *display = &data->display;
+ if (data->atomic_path)
+ require_atomic_async_cap(data);
+
for_each_pipe_with_valid_output(display, data->pipe, data->output) {
igt_display_reset(display);
@@ -712,6 +721,9 @@ static void run_test(data_t *data, void (*test)(data_t *))
static void run_test_with_modifiers(data_t *data, void (*test)(data_t *))
{
+ if (data->atomic_path)
+ require_atomic_async_cap(data);
+
for_each_pipe_with_valid_output(&data->display, data->pipe, data->output) {
test_init(data);
--
2.49.0
next prev parent reply other threads:[~2025-03-27 22:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 22:15 [PATCH v4 0/3] tests/kms_async_flips: Create subtest for overlay planes André Almeida
2025-03-27 22:15 ` André Almeida [this message]
2025-03-29 18:29 ` [PATCH v4 1/3] tests/kms_async_flips: Check for atomic async flip cap Melissa Wen
2025-03-27 22:16 ` [PATCH v4 2/3] kms_async_flips: Refactor data options André Almeida
2025-03-29 18:53 ` Melissa Wen
2025-03-27 22:16 ` [PATCH v4 3/3] tests/kms_async_flips: Create subtest for overlay planes André Almeida
2025-03-29 19:25 ` Melissa Wen
2025-04-01 21:29 ` André Almeida
2025-03-28 3:28 ` ✓ Xe.CI.BAT: success for tests/kms_async_flips: Create subtest for overlay planes (rev5) Patchwork
2025-03-28 3:50 ` ✓ i915.CI.BAT: " Patchwork
2025-03-28 7:22 ` Patchwork
2025-03-28 16:05 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-29 19:38 ` [PATCH v4 0/3] tests/kms_async_flips: Create subtest for overlay planes Melissa Wen
2025-04-06 17:31 ` ✗ Xe.CI.Full: failure for tests/kms_async_flips: Create subtest for overlay planes (rev5) Patchwork
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=20250327221601.19086-2-andrealmeid@igalia.com \
--to=andrealmeid@igalia.com \
--cc=alex.hung@amd.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jeevan.b@intel.com \
--cc=kamil.konieczny@linux.intel.com \
--cc=kernel-dev@igalia.com \
--cc=mwen@igalia.com \
--cc=siqueira@igalia.com \
--cc=vitaly.prosyak@amd.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