From: Jani Nikula <jani.nikula@intel.com>
To: Dave Airlie <airlied@gmail.com>,
Simona Vetter <simona.vetter@ffwll.ch>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Jani Nikula" <jani.nikula@linux.intel.com>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Matthew Brost" <matthew.brost@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Oded Gabbay" <ogabbay@kernel.org>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, dim-tools@lists.freedesktop.org,
"Ville Syrjala" <ville.syrjala@linux.intel.com>
Subject: [PULL] topic/pipe-reorder for drm-intel-next and possibly v7.1-rc1
Date: Wed, 15 Apr 2026 19:08:52 +0300 [thread overview]
Message-ID: <d69501d53c233386d70ed10290af24aafebf434f@intel.com> (raw)
Hi Dave & Linus -
This is a topic pull request for changing the pipe allocation order for
discrete platforms from the usual A,B,C,D to A,C,B,D. The goal is to
help pipe joiner configurations that reserve the adjacent pipe as the
secondary pipe without the user space knowing. More details in the
relevant commit message. The CRTC iteration is also changed to remain in
pipe order.
This has been a long time in the making, primarily because IGT basically
assumed CRTC index == pipe, and it took hundreds of commits from Ville
and me over several months to untangle it, and actually get CI results.
I'm going to merge this to drm-intel-next soon, and at this point in
time it would normally target v7.2.
We're fully aware this is beyond feature deadlines for v7.1 and it
hasn't seen linux-next. But in the off-chance you might consider also
pulling this as a fix for v7.1 (and really, distros might want this to
be backported to stable) I'm sending this as a separate topic pull
request.
I'm leaving it to your discretion.
BR,
Jani.
topic/pipe-reorder-2026-04-15:
drm/i915/display: change pipe allocation order for discrete platforms
The following changes since commit 4516432284e1b2ad9e70de8067f779c9c1072189:
ttm/pool: track allocated_pages per numa node. (2026-04-08 06:52:48 +1000)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/i915/kernel.git tags/topic/pipe-reorder-2026-04-15
for you to fetch changes up to 2c683e9b419328da3433a49f7c467da71aaf0469:
drm/i915/display: change pipe allocation order for discrete platforms (2026-04-15 13:30:26 +0300)
----------------------------------------------------------------
drm/i915/display: change pipe allocation order for discrete platforms
----------------------------------------------------------------
Jani Nikula (1):
drm/i915/display: change pipe allocation order for discrete platforms
Ville Syrjälä (2):
drm/i915/joiner: Make joiner "nomodeset" state copy independent of pipe order
drm/i915: Walk crtcs in pipe order
drivers/gpu/drm/i915/display/intel_crtc.c | 49 +++++++++++-
drivers/gpu/drm/i915/display/intel_display.c | 20 ++---
drivers/gpu/drm/i915/display/intel_display.h | 90 +++++++++-------------
drivers/gpu/drm/i915/display/intel_display_core.h | 3 +
.../gpu/drm/i915/display/intel_display_driver.c | 1 +
drivers/gpu/drm/i915/display/intel_display_types.h | 1 +
drivers/gpu/drm/xe/display/xe_display.c | 1 +
7 files changed, 95 insertions(+), 70 deletions(-)
--
Jani Nikula, Intel
next reply other threads:[~2026-04-15 16:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 16:08 Jani Nikula [this message]
2026-04-15 16:28 ` [PULL] topic/pipe-reorder for drm-intel-next and possibly v7.1-rc1 Linus Torvalds
2026-04-15 16:40 ` Linus Torvalds
2026-04-16 9:03 ` Jani Nikula
2026-04-22 0:44 ` pr-tracker-bot
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=d69501d53c233386d70ed10290af24aafebf434f@intel.com \
--to=jani.nikula@intel.com \
--cc=airlied@gmail.com \
--cc=dim-tools@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.brost@intel.com \
--cc=mripard@kernel.org \
--cc=ogabbay@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=simona.vetter@ffwll.ch \
--cc=thomas.hellstrom@linux.intel.com \
--cc=torvalds@linux-foundation.org \
--cc=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
--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