From: Juasheem Sultan <jdsultan@google.com>
To: intel-gfx@lists.freedesktop.org, intel_xe@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Manasi Navare <navaremanasi@google.com>,
Drew Davenport <ddavenport@google.com>,
Sean Paul <seanpaul@google.com>,
Samuel Jacob <samjaco@google.com>,
Rajat Jain <rajatja@google.com>,
Juasheem Sultan <jdsultan@google.com>
Subject: [RFC PATCH v3 0/2] Enable seamless boot (fastboot) for PTL
Date: Wed, 21 Jan 2026 12:46:51 -0800 [thread overview]
Message-ID: <20260121204705.432290-1-jdsultan@google.com> (raw)
Resending with cover letter from v2. There were no significant code
changes. Only resending due to mail failure.
This patch series is the second revision of a series of patches meant
to add support for seamless framebuffer handoff within the Xe driver.
It was tested on Panther Lake platforms.
The goal of this series is to achieve a flicker-free transition from
the bootloader (BIOS/UEFI) to the kernel driver by strictly adhering
to the hardware state established by the firmware.
Thank you for the feedback on the previous revision.
This new patch series was created with that feedback in mind. That
revision was too rough of an implementation that had a considerable
amount of useless code and fixed problems that it unecessarily
introduced. Because of that, I completely reworked and rewrote the
solution into a much smaller, efficient version that properly makes
use of the existing infrastructure. This patch series has two specific
focal points. It enables Xe to properly adopt a framebuffer from bios
by fixing how we read stolen memory and it synchronizes an inherited
crtc state with the new state so that we can perform an initial commit.
This allows us to achieve seamless handoff between the firmware and
kernel with minimal changes required.
---
Changes since v1
- v2 Complete rewrite of the code
- v3 Resending due to failure of patches to send
Juasheem Sultan (2):
drm/xe/display: Fix reading the framebuffer from stolen memory
drm/i915/display: Synchronize crtc_state for initial commit
drivers/gpu/drm/i915/display/intel_display.c | 19 ++++++++++++++++
drivers/gpu/drm/xe/display/xe_plane_initial.c | 22 ++++++++++++++++++-
2 files changed, 40 insertions(+), 1 deletion(-)
--
2.52.0.457.g6b5491de43-goog
next reply other threads:[~2026-01-21 20:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 20:46 Juasheem Sultan [this message]
2026-01-21 20:46 ` [RFC PATCH v3 1/2] drm/xe/display: Fix reading the framebuffer from stolen memory Juasheem Sultan
2026-01-21 20:46 ` [RFC PATCH v3 2/2] drm/i915/display: Synchronize crtc_state for initial commit Juasheem Sultan
2026-01-21 22:02 ` Manasi Navare
2026-01-22 15:29 ` Jani Nikula
2026-01-27 8:05 ` Juasheem Sultan
2026-02-03 18:18 ` Manasi Navare
2026-02-03 19:47 ` Jani Nikula
2026-02-03 21:03 ` Manasi Navare
2026-03-03 0:43 ` Manasi Navare
2026-03-03 9:44 ` Jani Nikula
2026-03-04 3:30 ` Juasheem Sultan
2026-01-21 21:29 ` ✗ Fi.CI.BUILD: failure for Enable seamless boot (fastboot) for PTL 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=20260121204705.432290-1-jdsultan@google.com \
--to=jdsultan@google.com \
--cc=ddavenport@google.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel_xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=navaremanasi@google.com \
--cc=rajatja@google.com \
--cc=rodrigo.vivi@intel.com \
--cc=samjaco@google.com \
--cc=seanpaul@google.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