From: Mark Yacoub <markyacoub@google.com>
To: igt-dev@lists.freedesktop.org
Cc: Louis Chauvet <louis.chauvet@bootlin.com>,
Mark Yacoub <markyacoub@google.com>
Subject: [PATCH i-g-t] tests/unigraf_lt: Restrict to Intel drivers
Date: Thu, 13 Aug 2026 13:11:56 -0400 [thread overview]
Message-ID: <20260813171156.2353078-1-markyacoub@google.com> (raw)
Currently, `igt_dp_force_link_retrain` natively maps to Intel's
i915 debugfs architecture. Thus, enforce
`igt_require_f(is_intel_device(drm_fd))` in the test fixture so
that this suite explicitly skips rather than blindly failing on
generic drivers. Other drivers should implement equivalent generic
IGT hooks before they can execute this verification.
Signed-off-by: Mark Yacoub <markyacoub@google.com>
---
tests/unigraf/unigraf_lt.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tests/unigraf/unigraf_lt.c b/tests/unigraf/unigraf_lt.c
index 81e6ecd3f..c0d1161f6 100644
--- a/tests/unigraf/unigraf_lt.c
+++ b/tests/unigraf/unigraf_lt.c
@@ -94,6 +94,8 @@ int igt_main()
igt_fixture() {
drm_fd = drm_open_driver(DRIVER_ANY);
igt_assert(drm_fd >= 0);
+ igt_require_f(is_intel_device(drm_fd),
+ "This test relies on Intel-specific debugfs endpoints (e.g., i915_dp_force_link_rate, i915_dp_force_lane_count) for link training verification. Other drivers should implement equivalent generic IGT hooks.\n");
igt_display_require(&display, drm_fd);
unigraf_require_device(drm_fd);
--
2.55.0.691.gc56d675ccc-goog
next reply other threads:[~2026-08-13 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 17:11 Mark Yacoub [this message]
2026-08-13 19:57 ` ✓ Xe.CI.BAT: success for tests/unigraf_lt: Restrict to Intel drivers Patchwork
2026-08-13 20:00 ` ✓ i915.CI.BAT: " Patchwork
2026-08-13 22:40 ` ✓ Xe.CI.FULL: " Patchwork
2026-08-14 4:04 ` ✗ i915.CI.Full: failure " 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=20260813171156.2353078-1-markyacoub@google.com \
--to=markyacoub@google.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=louis.chauvet@bootlin.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