From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Dave Airlie <airlied@gmail.com>, Simona Vetter <simona.vetter@ffwll.ch>
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
Subject: [PULL] drm-intel-next-fixes
Date: Thu, 5 Feb 2026 10:02:38 +0200 [thread overview]
Message-ID: <aYROngKfyUIyoQW0@jlahtine-mobl> (raw)
Hi Dave & Sima,
Here goes this weeks drm-intel-next-fixes PR towards 6.20/7.0-rc1.
Just one display fix for Xe3p_LPD pixel normalization.
Regards, Joonas
***
drm-intel-next-fixes-2026-02-05:
- Fix the pixel normalization handling for xe3p_lpd display
The following changes since commit ad3ebcc2d06875738cd463fb5424cda70cd94a34:
drm/i915/display: Prevent u64 underflow in intel_fbc_stolen_end (2026-01-26 11:39:57 +0200)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/i915/kernel.git tags/drm-intel-next-fixes-2026-02-05
for you to fetch changes up to 3e28a67a85f9b569066f6dfcddadb39294c0c9d4:
drm/i915/display: fix the pixel normalization handling for xe3p_lpd (2026-02-02 13:41:03 +0200)
----------------------------------------------------------------
- Fix the pixel normalization handling for xe3p_lpd display
----------------------------------------------------------------
Vinod Govindapillai (1):
drm/i915/display: fix the pixel normalization handling for xe3p_lpd
.../gpu/drm/i915/display/intel_display_device.h | 1 +
drivers/gpu/drm/i915/display/intel_fbc.c | 10 +++---
drivers/gpu/drm/i915/display/intel_fbc.h | 3 +-
drivers/gpu/drm/i915/display/skl_universal_plane.c | 36 +++++++++++-----------
4 files changed, 26 insertions(+), 24 deletions(-)
next reply other threads:[~2026-02-05 8:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 8:02 Joonas Lahtinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-22 7:53 [PULL] drm-intel-next-fixes Tvrtko Ursulin
2026-04-16 6:50 Tvrtko Ursulin
2026-02-20 8:31 Joonas Lahtinen
2026-02-13 10:53 Joonas Lahtinen
2026-01-29 8:11 Joonas Lahtinen
2026-01-22 8:02 Joonas Lahtinen
2025-08-05 7:48 Jani Nikula
2025-06-05 8:35 Joonas Lahtinen
2025-05-28 6:56 Joonas Lahtinen
2025-05-22 6:59 Joonas Lahtinen
2025-05-15 8:27 Joonas Lahtinen
2025-03-25 9:07 Jani Nikula
2024-11-21 8:37 Tvrtko Ursulin
2024-09-26 7:45 Joonas Lahtinen
2024-09-19 9:49 Joonas Lahtinen
2024-09-12 8:59 Joonas Lahtinen
2024-07-25 7:44 Tvrtko Ursulin
2024-07-18 9:30 Tvrtko Ursulin
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=aYROngKfyUIyoQW0@jlahtine-mobl \
--to=joonas.lahtinen@linux.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=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=tursulin@ursulin.net \
--cc=tzimmermann@suse.de \
/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