From: Sowmiya S <sowmiya.s@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: swati2.sharma@intel.com, karthik.b.s@intel.com,
Sowmiya S <sowmiya.s@intel.com>
Subject: [PATCH i-g-t v1 0/2] Make pipe assignment joiner-aware
Date: Thu, 19 Feb 2026 13:33:38 +0530 [thread overview]
Message-ID: <20260219080349.139498-1-sowmiya.s@intel.com> (raw)
kms_pipe_stress assumed a 1:1 output-to-pipe mapping (pipe++),
which breaks on joiner configurations where one output may consume multiple
consecutive pipes.
This patch series switch assignment to igt_assign_pipes_for_outputs() and
map outputs by their driving CRTC/pipe. Skip outputs that cannot be
assigned and continue when at least one output is valid.
Store highest_mode as owned copies to avoid stale connector mode pointers
after output refresh. Iterate stress/setup by assigned pipe(output_by_pipe)
instead of connected-output order. Keep progressive modeset flow by
clearing temporary CRTC mappings after assignment.
Use min_t(int, ...) for source size calculations to start scaling from a
size guaranteed to fit in the FB.
*** BLURB HERE ***
Sowmiya S (2):
tests/kms_pipe_stress: make pipe assignment joiner-aware
tests/meson.build: Join header file
tests/intel/kms_pipe_stress: Clamp the source size to the FB bounds
tests/intel/kms_pipe_stress.c | 209 ++++++++++++++++++----------------
tests/meson.build | 1 +
2 files changed, 110 insertions(+), 100 deletions(-)
--
2.48.1
next reply other threads:[~2026-02-19 7:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 8:03 Sowmiya S [this message]
2026-02-19 8:03 ` [PATCH i-g-t v1 1/2] tests/kms_pipe_stress: make pipe assignment joiner-aware Sowmiya S
2026-02-19 8:03 ` [PATCH i-g-t v1 2/2] tests/intel/kms_pipe_stress: Clamp the source size to the FB bounds Sowmiya S
2026-02-19 11:17 ` ✓ Xe.CI.BAT: success for Make pipe assignment joiner-aware Patchwork
2026-02-19 11:31 ` ✓ i915.CI.BAT: " Patchwork
2026-02-19 13:36 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-19 15:18 ` ✗ i915.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=20260219080349.139498-1-sowmiya.s@intel.com \
--to=sowmiya.s@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=karthik.b.s@intel.com \
--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