From: Jani Nikula <jani.nikula@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: jani.nikula@intel.com, ville.syrjala@linux.intel.com
Subject: [PATCH i-g-t 0/3] lib/kms: make for_each_crtc_with_single_output() independent of pipes
Date: Mon, 23 Mar 2026 14:06:23 +0200 [thread overview]
Message-ID: <cover.1774267502.git.jani.nikula@intel.com> (raw)
A slightly tricky series to make for_each_crtc_with_single_output()
independent of pipes, while retaining pipe order iteration on Intel
devices.
Jani Nikula (3):
lib/kms: don't special case igt_get_single_output_for_crtc()
implementation
lib/kms: refactor for_each_crtc_with_single_output() to avoid
igt_crtc_for_pipe()
lib/kms: use CRTC index for __igt_output_crtc_populate()
lib/igt_kms.c | 40 +++++++++++++++++++++++++++++++---------
lib/igt_kms.h | 23 ++++++++++++++---------
2 files changed, 45 insertions(+), 18 deletions(-)
--
2.47.3
next reply other threads:[~2026-03-23 12:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 12:06 Jani Nikula [this message]
2026-03-23 12:06 ` [PATCH i-g-t 1/3] lib/kms: don't special case igt_get_single_output_for_crtc() implementation Jani Nikula
2026-03-23 12:06 ` [PATCH i-g-t 2/3] lib/kms: refactor for_each_crtc_with_single_output() to avoid igt_crtc_for_pipe() Jani Nikula
2026-03-23 12:06 ` [PATCH i-g-t 3/3] lib/kms: use CRTC index for __igt_output_crtc_populate() Jani Nikula
2026-03-26 11:36 ` Ville Syrjälä
2026-03-26 12:36 ` Jani Nikula
2026-03-23 16:38 ` ✓ Xe.CI.BAT: success for lib/kms: make for_each_crtc_with_single_output() independent of pipes Patchwork
2026-03-23 16:54 ` ✓ i915.CI.BAT: " Patchwork
2026-03-23 23:39 ` ✓ Xe.CI.FULL: " Patchwork
2026-03-24 1:24 ` ✗ 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=cover.1774267502.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.