From: Jani Nikula <jani.nikula@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: ville.syrjala@linux.intel.com, jani.nikula@intel.com
Subject: [PATCH i-g-t 0/5] igt: reduce igt_crtc_for_pipe() usage
Date: Fri, 6 Mar 2026 15:23:53 +0200 [thread overview]
Message-ID: <cover.1772803372.git.jani.nikula@intel.com> (raw)
Add igt_next_crtc() and igt_random_crtc() to let us remove a few more
igt_crtc_for_pipe() calls.
Jani Nikula (5):
lib/kms: add igt_next_crtc()
tests/intel/gem_pxp: use igt_next_crtc()
tests/intel/xe_pxp: use igt_next_crtc()
tests/kms_multipipe_modeset: use igt_next_crtc()
lib/kms: add igt_random_crtc() and use it in gem_eio
lib/igt_kms.c | 39 +++++++++++++++++++++++++++++++++++
lib/igt_kms.h | 2 ++
tests/intel/gem_eio.c | 7 +------
tests/intel/gem_pxp.c | 7 +++----
tests/intel/xe_pxp.c | 15 ++++++--------
tests/kms_multipipe_modeset.c | 32 +++++++++++++---------------
6 files changed, 65 insertions(+), 37 deletions(-)
--
2.47.3
next reply other threads:[~2026-03-06 13:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 13:23 Jani Nikula [this message]
2026-03-06 13:23 ` [PATCH i-g-t 1/5] lib/kms: add igt_next_crtc() Jani Nikula
2026-03-06 13:23 ` [PATCH i-g-t 2/5] tests/intel/gem_pxp: use igt_next_crtc() Jani Nikula
2026-03-06 13:23 ` [PATCH i-g-t 3/5] tests/intel/xe_pxp: " Jani Nikula
2026-03-06 13:23 ` [PATCH i-g-t 4/5] tests/kms_multipipe_modeset: " Jani Nikula
2026-03-06 14:04 ` Ville Syrjälä
2026-03-09 9:27 ` Jani Nikula
2026-03-06 13:23 ` [PATCH i-g-t 5/5] lib/kms: add igt_random_crtc() and use it in gem_eio Jani Nikula
2026-03-06 14:07 ` [PATCH i-g-t 0/5] igt: reduce igt_crtc_for_pipe() usage Ville Syrjälä
2026-03-06 14:59 ` ✓ i915.CI.BAT: success for " Patchwork
2026-03-06 15:04 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-07 16:08 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-03-07 16:12 ` ✗ 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=cover.1772803372.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=ville.syrjala@linux.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