From: Mohammed Bilal <mohammed.bilal@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: jeevan.b@intel.com, kunal1.joshi@intel.com,
sameer.lattannavar@intel.com, karthik.b.s@intel.com,
Mohammed Bilal <mohammed.bilal@intel.com>
Subject: [PATCH i-g-t v5 0/2] Fix chamelium port allocation during igt_fixture
Date: Tue, 6 Jan 2026 21:02:30 +0530 [thread overview]
Message-ID: <20260106153232.79004-1-mohammed.bilal@intel.com> (raw)
The current fixture implementation executes even for unrelated subtests,
causing false failures when expected inputs were not present.
Refactor the DP/HDMI/VGA hotplug tests to use a common
connector lookup pattern so that each test skips cleanly.
v3:
- Introduce a unified connector test macro (Sebastien)
- Remove unused variable (Sebastien)
- Drop per-connector fixture usage (Sebastien)
- Refactor DP/HDMI/VGA hotplug tests (Sebastien)
v4:
- Rename helper to igt_chamelium_get_port (Jeevan)
- Add documentation for helper and macro (Jeevan)
- Use lowercase name for test macro (Sebastien)
v5:
-Iterate and test all matching connected ports (Kunal)
Mohammed Bilal (2):
lib/igt_chamelium: Add connector_test() macro
tests/chamelium/kms_chamelium_hpd: use helper function for connector
lookup in DP/HDMI/VGA tests
lib/igt_chamelium.h | 31 ++++
tests/chamelium/kms_chamelium_hpd.c | 238 ++++++++++++----------------
2 files changed, 128 insertions(+), 141 deletions(-)
--
2.48.1
next reply other threads:[~2026-01-06 15:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 15:32 Mohammed Bilal [this message]
2026-01-06 15:32 ` [PATCH i-g-t v5 1/2] lib/igt_chamelium: Add connector_test() macro Mohammed Bilal
2026-01-06 15:32 ` [PATCH i-g-t v5 2/2] tests/chamelium/kms_chamelium_hpd: use helper function for connector lookup in DP/HDMI/VGA tests Mohammed Bilal
2026-01-06 16:07 ` ✓ Xe.CI.BAT: success for Fix chamelium port allocation during igt_fixture Patchwork
2026-01-06 16:24 ` ✗ i915.CI.BAT: failure " Patchwork
2026-01-06 17:37 ` ✗ Xe.CI.Full: " 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=20260106153232.79004-1-mohammed.bilal@intel.com \
--to=mohammed.bilal@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jeevan.b@intel.com \
--cc=karthik.b.s@intel.com \
--cc=kunal1.joshi@intel.com \
--cc=sameer.lattannavar@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