From: Kunal Joshi <kunal1.joshi@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Kunal Joshi <kunal1.joshi@intel.com>
Subject: [PATCH] tests/chamelium/kms_chamelium_color: force connector reprobe after plugging ports
Date: Wed, 15 Jan 2025 20:45:07 +0530 [thread overview]
Message-ID: <20250115151507.2023293-1-kunal1.joshi@intel.com> (raw)
Force reprobe connector status after plugging to assure
we always have DRM_MODE_CONNECTED status for the connector
before proceding with the test.
Fixes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/2371
Signed-off-by: Kunal Joshi <kunal1.joshi@intel.com>
---
tests/chamelium/kms_chamelium_color.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/tests/chamelium/kms_chamelium_color.c b/tests/chamelium/kms_chamelium_color.c
index 5550cec22..7c88c022c 100644
--- a/tests/chamelium/kms_chamelium_color.c
+++ b/tests/chamelium/kms_chamelium_color.c
@@ -749,8 +749,13 @@ igt_main
* discovered ports, just incase they are not plugged
* we currently skip in test_setup
*/
- for( i = 0; i < data.port_count; i++)
+ for (i = 0; i < data.port_count; i++) {
chamelium_plug(data.chamelium, data.ports[i]);
+ igt_assert_f(chamelium_reprobe_connector(&data.display,
+ data.chamelium,
+ data.ports[i]) == DRM_MODE_CONNECTED,
+ "Output not connected\n");
+ }
kmstest_set_vt_graphics_mode();
}
--
2.25.1
next reply other threads:[~2025-01-15 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 15:15 Kunal Joshi [this message]
2025-01-16 4:10 ` ✗ Xe.CI.BAT: failure for tests/chamelium/kms_chamelium_color: force connector reprobe after plugging ports Patchwork
2025-01-16 4:14 ` ✓ i915.CI.BAT: success " Patchwork
2025-01-16 7:42 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-16 10:39 ` [PATCH] " Sharma, Swati2
2025-01-16 11:22 ` Sharma, Swati2
2025-01-17 9:21 ` ✗ i915.CI.Full: failure for " 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=20250115151507.2023293-1-kunal1.joshi@intel.com \
--to=kunal1.joshi@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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