From: Jeevan B <jeevan.b@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: swati2.sharma@intel.com, Jeevan B <jeevan.b@intel.com>
Subject: [PATCH 3/3] tests/kms_display_modes: Skip test if joiner display is connected
Date: Mon, 25 Nov 2024 22:04:26 +0530 [thread overview]
Message-ID: <20241125163426.382975-4-jeevan.b@intel.com> (raw)
In-Reply-To: <20241125163426.382975-1-jeevan.b@intel.com>
High-resolution displays that support joiner modes can cause extended mode
tests to fail. This commit introduces a check to skip these tests if a
joiner mode display is connected, ensuring the test suite runs smoothly
without unnecessary failures.
v2: Add output name in skip message.
Signed-off-by: Jeevan B <jeevan.b@intel.com>
Reviewed-by: Swati Sharma <swati2.sharma@intel.com>
---
tests/kms_display_modes.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tests/kms_display_modes.c b/tests/kms_display_modes.c
index f1d8ab03d..716e07a40 100644
--- a/tests/kms_display_modes.c
+++ b/tests/kms_display_modes.c
@@ -318,6 +318,9 @@ igt_main
igt_display_require_output(&data.display);
for_each_connected_output(&data.display, output) {
+ igt_skip_on_f(is_joiner_mode(data.drm_fd, output),
+ "Joiner mode found on output %s, skipping the test\n",
+ output->name);
data.mst_output[count++] = output;
if (output_is_dp_mst(&data, output, dp_mst_outputs))
dp_mst_outputs++;
--
2.25.1
next prev parent reply other threads:[~2024-11-25 16:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 16:34 [PATCH 0/3] Skip test if joiner display is connected Jeevan B
2024-11-25 16:34 ` [PATCH 1/3] lib/igt_kms: Add is_joiner_mode function Jeevan B
2024-11-25 16:34 ` [PATCH 2/3] tests/kms_async_flips: Skip async flips on joiner output Jeevan B
2024-11-26 12:11 ` Sharma, Swati2
2024-11-25 16:34 ` Jeevan B [this message]
2024-11-25 23:59 ` ✓ Xe.CI.BAT: success for Skip test if joiner display is connected (rev2) Patchwork
2024-11-26 0:16 ` ✗ i915.CI.BAT: failure " Patchwork
2024-11-26 3:12 ` ✗ Xe.CI.Full: " Patchwork
2024-11-26 10:18 ` B, Jeevan
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=20241125163426.382975-4-jeevan.b@intel.com \
--to=jeevan.b@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=swati2.sharma@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