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 v1 1/2] lib/igt_kms: Add platform-specific joiner exception mode handling
Date: Thu, 23 Jul 2026 19:13:53 +0530 [thread overview]
Message-ID: <20260723134355.337709-2-sowmiya.s@intel.com> (raw)
In-Reply-To: <20260723134355.337709-1-sowmiya.s@intel.com>
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 IS_NOVALAKE() in a new mode_needs_joiner_exception() helper, and
wire it into igt_bigjoiner_possible(). Also add IS_NOVALAKE() to
intel_chipset.h as a combined IS_NOVALAKE_S() || IS_NOVALAKE_P() macro.
Signed-off-by: Sowmiya S <sowmiya.s@intel.com>
---
lib/igt_kms.c | 52 +++++++++++++++++++++++++++++++++++++++++++++++++--
1 file changed, 50 insertions(+), 2 deletions(-)
diff --git a/lib/igt_kms.c b/lib/igt_kms.c
index 2eefb773b..bfa6dfc0e 100644
--- a/lib/igt_kms.c
+++ b/lib/igt_kms.c
@@ -7058,6 +7058,52 @@ int intel_get_max_pipe_hdisplay(int drm_fd)
HDISPLAY_5K_PER_PIPE;
}
+struct joiner_mode_exception {
+ uint16_t hdisplay, vdisplay;
+ uint32_t clock;
+};
+
+static bool match_joiner_exception(drmModeModeInfo *mode,
+ const struct joiner_mode_exception *list,
+ int count)
+{
+ for (int i = 0; i < count; i++) {
+ if (mode->hdisplay == list[i].hdisplay &&
+ mode->vdisplay == list[i].vdisplay &&
+ mode->clock == list[i].clock)
+ return true;
+ }
+
+ return false;
+}
+
+/* NVL: higher max_dotclock allows clocks that still need joiner */
+static const struct joiner_mode_exception nvl_joiner_exception_modes[] = {
+ { 6144, 3456, 1413390 }, /* 6144x3456@60Hz */
+};
+
+/*
+ * mode_needs_joiner_exception - check if a mode requires joiner via explicit exception
+ * @drm_fd: drm file descriptor
+ * @mode: libdrm mode
+ *
+ * On some platforms, a higher max_dotclock means certain modes won't trigger
+ * the standard clock or hdisplay checks even though the kernel enables joiner
+ * for them. Each platform has its own exception list.
+ *
+ * Returns: True if the mode is a known joiner exception, else False.
+ */
+static bool mode_needs_joiner_exception(int drm_fd, drmModeModeInfo *mode)
+{
+ uint16_t dev_id = intel_get_drm_devid(drm_fd);
+
+ if (IS_NOVALAKE_P(dev_id) || IS_NOVALAKE_S(dev_id))
+ return match_joiner_exception(mode, nvl_joiner_exception_modes,
+ ARRAY_SIZE(nvl_joiner_exception_modes));
+
+ return false;
+}
+
/**
* igt_bigjoiner_possible:
* @drm_fd: drm file descriptor
@@ -7066,13 +7112,15 @@ int intel_get_max_pipe_hdisplay(int drm_fd)
*
* Bigjoiner is required when the requested mode exceeds single-pipe
* platform limits, i.e. hdisplay is above the platform threshold or
- * clock is above @max_dotclock.
+ * clock is above @max_dotclock. On NVL, the higher max_dotclock means
+ * some modes (e.g. 6144x3456@60) need an explicit exception check.
*
* Returns: True if mode requires Bigjoiner, else False.
*/
bool igt_bigjoiner_possible(int drm_fd, drmModeModeInfo *mode, int max_dotclock)
{
- return (mode->hdisplay > intel_get_max_pipe_hdisplay(drm_fd) ||
+ return (mode_needs_joiner_exception(drm_fd, mode) ||
+ mode->hdisplay > intel_get_max_pipe_hdisplay(drm_fd) ||
mode->clock > max_dotclock);
}
--
2.43.0
next prev parent reply other threads:[~2026-07-23 13:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 13:43 [PATCH i-g-t v1 0/2] Add platform-specific joiner exception mode handling Sowmiya S
2026-07-23 13:43 ` Sowmiya S [this message]
2026-07-23 13:43 ` [PATCH i-g-t v1 2/2] lib/igt_kms: Skip joiner exception modes in boundary non-joiner search Sowmiya S
2026-07-23 14:49 ` ✓ Xe.CI.BAT: success for Add platform-specific joiner exception mode handling Patchwork
2026-07-23 14:51 ` ✓ i915.CI.BAT: " 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=20260723134355.337709-2-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