From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: Simona Vetter <simona.vetter@ffwll.ch>, Dave Airlie <airlied@gmail.com>
Cc: dim-tools@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
"Oded Gabbay" <ogabbay@kernel.org>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Matthew Brost" <matthew.brost@intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Tvrtko Ursulin" <tursulin@ursulin.net>,
"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
"Jani Nikula" <jani.nikula@linux.intel.com>
Subject: [PULL] drm-misc-fixes
Date: Thu, 22 Jan 2026 10:50:00 +0100 [thread overview]
Message-ID: <4c2f66df-c990-448a-b466-99a66981272b@linux.intel.com> (raw)
Hi Dave, Sima,
Here's a pull request for v6.19. There were some small fixes related to colorops,
including a last minute fix to correct the intel pipeline ordering.
There are still some leaks in the unload and load failure paths,
https://patchwork.freedesktop.org/series/159261/ patches 5-13, but I feel those
can be addressed separately with less urgency so late in the release cycle.
Kind regards,
~Maarten Lankhorst
drm-misc-fixes-2026-01-22:
drm-msic-fixes for v6.19:
imagination:
- sync wait for logtype update completion to ensure FW trace is
available
bridge/synopsis:
- Fix error paths in dw_dp_bind
nouveau:
- Add and implement missing DSB connector types, and improve unknown
connector handling.
- Set missing atomic function ops.
intel/display, amd, vkms:
- (all) Fix a leak during device init where strings were leaked.
- (intel) Place 3D lut at correct place in colorops pipeline.
The following changes since commit 9dd1f5f3eb8cb175e2f7fd2a685bdb6b1bd2a726:
Merge tag 'drm-misc-fixes-2026-01-16' of https://gitlab.freedesktop.org/drm/misc/kernel into drm-fixes (2026-01-16 20:27:21 +0100)
are available in the Git repository at:
https://gitlab.freedesktop.org/drm/misc/kernel.git tags/drm-misc-fixes-2026-01-22
for you to fetch changes up to 0a095b64fa5b4b1edfeb2e9b1751e044230c5d73:
drm/i915/display: Fix color pipeline enum name leak (2026-01-22 10:26:55 +0100)
----------------------------------------------------------------
drm-msic-fixes for v6.19:
imagination:
- sync wait for logtype update completion to ensure FW trace is
available
bridge/synopsis:
- Fix error paths in dw_dp_bind
nouveau:
- Add and implement missing DSB connector types, and improve unknown
connector handling.
- Set missing atomic function ops.
intel/display, amd, vkms:
- (intel) Place 3D lut at correct place in colorops pipeline.
- (all) Fix a leak during device init where strings were leaked.
----------------------------------------------------------------
Alex Ramírez (2):
drm/nouveau: add missing DCB connector types
drm/nouveau: implement missing DCB connector types; gracefully handle unknown connectors
Brajesh Gupta (1):
drm/imagination: Wait for FW trace update command completion
Chaitanya Kumar Borah (4):
drm/i915/color: Place 3D LUT after CSC in plane color pipeline
drm/amd/display: Fix color pipeline enum name leak
drm/vkms: Fix color pipeline enum name leak
drm/i915/display: Fix color pipeline enum name leak
Lyude Paul (1):
drm/nouveau/disp: Set drm_mode_config_funcs.atomic_(check|commit)
Maarten Lankhorst (1):
Merge remote-tracking branch 'drm/drm-fixes' into drm-misc-fixes
Osama Abdelkader (1):
drm/bridge: synopsys: dw-dp: fix error paths of dw_dp_bind
.../drm/amd/display/amdgpu_dm/amdgpu_dm_colorop.c | 4 +-
.../drm/amd/display/amdgpu_dm/amdgpu_dm_plane.c | 13 ++-
drivers/gpu/drm/bridge/synopsys/dw-dp.c | 20 +++--
.../gpu/drm/i915/display/intel_color_pipeline.c | 36 ++++----
drivers/gpu/drm/imagination/pvr_fw_trace.c | 8 +-
.../drm/nouveau/include/nvkm/subdev/bios/conn.h | 95 +++++++++++++++++-----
drivers/gpu/drm/nouveau/nouveau_display.c | 2 +
drivers/gpu/drm/nouveau/nvkm/engine/disp/uconn.c | 73 ++++++++++++-----
drivers/gpu/drm/vkms/vkms_colorop.c | 15 ++--
9 files changed, 192 insertions(+), 74 deletions(-)
next reply other threads:[~2026-01-22 9:50 UTC|newest]
Thread overview: 101+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 9:50 Maarten Lankhorst [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-04-09 8:15 [PULL] drm-misc-fixes Maxime Ripard
2026-04-02 7:52 Maxime Ripard
2026-03-26 7:17 Maxime Ripard
2026-03-19 7:20 Maxime Ripard
2026-03-12 7:30 Maxime Ripard
2026-03-06 6:41 Maxime Ripard
2026-03-05 8:09 Maxime Ripard
2026-02-26 8:36 Maxime Ripard
2026-02-05 9:53 Maarten Lankhorst
2026-01-29 17:01 Maarten Lankhorst
2026-01-16 11:46 Maarten Lankhorst
2026-01-07 9:45 Maarten Lankhorst
2025-12-30 19:40 Maarten Lankhorst
2025-12-18 10:05 Maarten Lankhorst
2025-12-10 11:29 Maarten Lankhorst
2025-11-27 8:10 Thomas Zimmermann
2025-11-20 15:13 Thomas Zimmermann
2025-11-13 13:23 Thomas Zimmermann
2025-11-06 13:12 Thomas Zimmermann
2025-10-30 19:56 Thomas Zimmermann
2025-10-31 18:10 ` Simona Vetter
2025-10-23 8:34 Thomas Zimmermann
2025-10-24 11:36 ` Simona Vetter
2025-10-16 14:16 Thomas Zimmermann
2025-10-09 12:00 Thomas Zimmermann
2025-09-25 11:32 Maxime Ripard
2025-09-18 8:24 Maxime Ripard
2025-09-11 16:04 Maxime Ripard
2025-09-03 7:57 Maxime Ripard
2025-08-28 6:32 Maxime Ripard
2025-08-21 8:12 Maxime Ripard
2025-07-23 9:18 Maarten Lankhorst
2025-07-16 7:42 Maarten Lankhorst
2025-07-10 8:59 Maarten Lankhorst
2025-07-11 12:15 ` Simona Vetter
2025-07-03 15:26 Maarten Lankhorst
2025-06-27 7:04 Maarten Lankhorst
2025-06-19 8:12 Maarten Lankhorst
2025-06-12 11:53 Maarten Lankhorst
2025-06-06 7:28 Thomas Zimmermann
2025-06-06 13:03 ` Simona Vetter
2025-05-28 15:35 Thomas Zimmermann
2025-06-06 12:38 ` Simona Vetter
2025-05-22 11:49 Thomas Zimmermann
2025-05-15 12:55 Thomas Zimmermann
2025-05-08 10:49 Thomas Zimmermann
2025-04-30 8:24 Maxime Ripard
2025-04-22 15:12 Thomas Zimmermann
2025-04-17 8:40 Thomas Zimmermann
2025-04-10 12:24 Thomas Zimmermann
2025-03-20 8:38 Maxime Ripard
2025-03-13 7:36 Maxime Ripard
2025-03-06 10:32 Maxime Ripard
2025-02-27 14:10 Maxime Ripard
2025-02-20 8:30 Maxime Ripard
2025-02-13 15:30 Maxime Ripard
2025-02-06 9:15 Maxime Ripard
2025-01-24 8:29 Thomas Zimmermann
2025-01-24 10:42 ` Simona Vetter
2025-01-15 9:22 Maarten Lankhorst
2025-01-02 8:47 Maarten Lankhorst
2024-12-19 18:10 Maarten Lankhorst
2024-12-05 19:48 Maarten Lankhorst
2024-11-28 13:59 Thomas Zimmermann
2024-11-21 13:18 Thomas Zimmermann
2024-11-14 14:22 Thomas Zimmermann
2024-11-08 8:50 Thomas Zimmermann
2024-10-31 14:43 Thomas Zimmermann
2024-10-24 12:49 Thomas Zimmermann
2024-10-17 11:55 Thomas Zimmermann
2024-10-10 13:37 Thomas Zimmermann
2024-10-02 15:15 Thomas Zimmermann
2024-09-26 12:10 Thomas Zimmermann
2024-09-12 8:49 Maxime Ripard
2024-09-05 14:19 Maxime Ripard
2024-08-29 14:51 Maxime Ripard
2024-08-22 12:39 Thomas Zimmermann
2024-08-15 13:17 Thomas Zimmermann
2024-08-08 7:48 Maxime Ripard
2024-08-01 9:00 Maxime Ripard
2024-07-11 9:51 Maarten Lankhorst
2024-07-04 12:27 Maarten Lankhorst
2024-07-04 14:49 ` Daniel Vetter
2024-06-26 15:35 Maarten Lankhorst
2024-06-14 8:13 Maarten Lankhorst
2024-06-06 22:09 Maarten Lankhorst
2024-05-30 19:23 Thomas Zimmermann
2024-05-23 18:47 Thomas Zimmermann
2024-05-16 7:26 Thomas Zimmermann
2024-05-10 7:20 Thomas Zimmermann
2024-05-02 19:21 Thomas Zimmermann
2024-04-25 10:24 Thomas Zimmermann
2024-04-18 7:22 Thomas Zimmermann
2024-04-11 7:34 Thomas Zimmermann
2024-04-04 10:48 Thomas Zimmermann
2024-03-28 13:44 Thomas Zimmermann
2024-03-07 8:44 Maxime Ripard
2024-02-29 13:37 Maxime Ripard
2024-02-29 13:54 ` Matthew Auld
2024-03-06 14:26 ` Maxime Ripard
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=4c2f66df-c990-448a-b466-99a66981272b@linux.intel.com \
--to=maarten.lankhorst@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=joonas.lahtinen@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