igt-dev.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
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/2] fix CRTC index to pipe conversion, cleanup
Date: Thu, 20 Nov 2025 12:23:12 +0200	[thread overview]
Message-ID: <cover.1763634045.git.jani.nikula@intel.com> (raw)

There's a bunch of conflation with CRTC index and pipe usage in IGT. Fix
one obvious mistake, and drop the old ioctl fallback for CRTC id to pipe
mapping.

There's likely more to come, but start off small.


Jani Nikula (2):
  lib/igt_kms: Always return CRTC index from
    kmstest_get_pipe_from_crtc_id()
  lib/igt_kms: Drop the ioctl fallback for CRTC id to pipe mapping

 lib/igt_kms.c | 45 +++++++++------------------------------------
 1 file changed, 9 insertions(+), 36 deletions(-)

-- 
2.47.3


             reply	other threads:[~2025-11-20 10:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20 10:23 Jani Nikula [this message]
2025-11-20 10:23 ` [PATCH i-g-t 1/2] lib/igt_kms: Always return CRTC index from kmstest_get_pipe_from_crtc_id() Jani Nikula
2025-11-20 10:23 ` [PATCH i-g-t 2/2] lib/igt_kms: Drop the ioctl fallback for CRTC id to pipe mapping Jani Nikula
2025-11-20 14:05   ` Ville Syrjälä
2025-11-20 14:58     ` Jani Nikula
2025-11-20 11:35 ` ✗ i915.CI.BAT: failure for fix CRTC index to pipe conversion, cleanup Patchwork
2025-11-20 12:46   ` Jani Nikula
2025-11-25  7:02     ` Ravali, JupallyX
2025-11-20 12:09 ` ✓ Xe.CI.BAT: success " Patchwork
2025-11-20 14:39 ` ✓ Xe.CI.Full: " Patchwork
2025-11-25  6:33 ` ✓ i915.CI.BAT: " Patchwork
2025-11-25 14:00 ` ✗ 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.1763634045.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;
as well as URLs for NNTP newsgroup(s).