Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sowmiya S <sowmiya.s@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: swati2.sharma@intel.com, santhosh.reddy.guddati@intel.com,
	Sowmiya S <sowmiya.s@intel.com>
Subject: [PATCH i-g-t v3 0/2] Add platform-specific joiner exception mode handling
Date: Wed,  5 Aug 2026 14:04:52 +0530	[thread overview]
Message-ID: <20260805083454.708311-1-sowmiya.s@intel.com> (raw)

    On NVL (display_ver=35), a higher max_dotclock causes modes like
6144x3456@60 to pass the standard igt_bigjoiner_possible() checks,
yet the kernel still enables joiner for them. Introduce per-platform
exception mode lists (e.g. nvl_joiner_exception_modes[]) dispatched
via novalake check in a new mode_needs_joiner_exception() helper, and
wire it into igt_bigjoiner_possible().
Fix intel_boundary_non_joiner_mode_found() to skip exception modes,
preventing test_basic_max_non_joiner from incorrectly selecting a
joiner-required mode as a non-joiner boundary mode.

Sowmiya S (2):
  lib/igt_kms: Add platform-specific joiner exception mode handling
  lib/igt_kms: Skip joiner exception modes in boundary non-joiner search

 lib/igt_kms.c | 64 +++++++++++++++++++++++++++++++++++++++++++++++++--
 1 file changed, 62 insertions(+), 2 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-08-05  8:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05  8:34 Sowmiya S [this message]
2026-08-05  8:34 ` [PATCH i-g-t v3 1/2] lib/igt_kms: Add platform-specific joiner exception mode handling Sowmiya S
2026-08-05  8:34 ` [PATCH i-g-t v3 2/2] lib/igt_kms: Skip joiner exception modes in boundary non-joiner search Sowmiya S
2026-08-05 22:37 ` ✓ Xe.CI.BAT: success for Add platform-specific joiner exception mode handling (rev3) Patchwork
2026-08-05 23:10 ` ✓ i915.CI.BAT: " Patchwork
2026-08-06  7:39 ` ✓ Xe.CI.FULL: " Patchwork
2026-08-06  9:31 ` ✗ i915.CI.Full: failure " Patchwork
2026-08-07  5:15 ` ✓ i915.CI.Full: success " 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=20260805083454.708311-1-sowmiya.s@intel.com \
    --to=sowmiya.s@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=santhosh.reddy.guddati@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