[PATCH 1/2] drm/rockchip: vop2: Add delay between poll registers

From: Andy Yan According to the implementation of read_poll_timeout_atomic, if the delay time is 0, it will only use a simple loop based on timeout_us to decrement the count. Therefore, the final timeout time will differ significantly from the setted timteout time. So, here we set a specific dela

[PATCH 2/2] drm/rockchip: vop2: Only wait for changed layer cfg done when there is pending cfgdone bits

From: Andy Yan The write of cfgdone bits always done at .atomic_flush. When userspace makes plane zpos changes of two crtc within one commit, at the .atomic_begin stage, crtcN will never receive the "layer change cfg done" event of crtcM because crtcM has not yet written "cfgdone". So only wait w

[PATCH v3 3/3] panthor: dump task pid and comm on gpu errors

It is useful to know which tasks cause gpu errors. Signed-off-by: Chia-I Wu Reviewed-by: Steven Price --- drivers/gpu/drm/panthor/panthor_sched.c | 24 +++- 1 file changed, 19 insertions(+), 5 deletions(-) diff --git a/drivers/gpu/drm/panthor/panthor_sched.c b/drivers/gpu/

[PATCH v3 1/3] panthor: set owner field for driver fops

It allows us to get rid of manual try_module_get / module_put. Signed-off-by: Chia-I Wu Reviewed-by: Boris Brezillon Reviewed-by: Steven Price --- drivers/gpu/drm/panthor/panthor_drv.c | 14 +++--- 1 file changed, 3 insertions(+), 11 deletions(-) diff --git a/drivers/gpu/drm/panthor/p

[PATCH v3 0/3] panthor: print task pid and comm on gpu errors

This series saves task pid and comm in panthor_group and prints task pid and comm on gpu errors. v3: fix new kerneldoc warnings v2: save the task info in panthor_group on panthor_group_create, rather than in panthor_file on panthor_open, because, when the two differ, we are more interested

[PATCH v2 0/5] Add Type-C DP support for RK3399 EVB IND board

From: Chaoyi Chen The RK3399 has two USB/DP combo PHY and one CDN-DP controller. And the CDN-DP can be switched to output to one of the PHYs. For USB Type-C interfaces, an external chip assists the PHY in handling altmode switching and orientation switching. Their connection diagram is shown bel

Re: linux-next: manual merge of the drm tree with the drm-misc-fixes tree

Hi Am 18.07.25 um 06:41 schrieb Stephen Rothwell: Hi all, Today's linux-next merge of the drm tree got a conflict in: drivers/gpu/drm/virtio/virtgpu_prime.c between commit: 0ecfb8ddb953 ("Revert "drm/virtio: Use dma_buf from GEM object instance"") from the drm-misc-fixes tree and comm

[PATCH v2 4/5] arm64: dts: rockchip: Add missing dp_out port for RK3399 CDN-DP

From: Chaoyi Chen Let's make the ports nodes of cdn_dp in the same style as the other display interface, and match the style of ports's yaml. Signed-off-by: Chaoyi Chen --- arch/arm64/boot/dts/rockchip/rk3399-base.dtsi | 12 +++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --

[PATCH v2 3/5] drm/rockchip: cdn-dp: Support handle lane info and HPD without extcon

From: Chaoyi Chen This patch add support for get PHY lane info and handle HPD state without help of extcon. There is no extcon needed if the Type-C controller is present. In this case, cdn_dp_hpd_notify() will handle HPD event from USB/DP combo PHY, and the lane info can be get from PHY instead

[PATCH v2 5/5] arm64: dts: rockchip: rk3399-evb-ind: Add support for DisplayPort

From: Chaoyi Chen The RK3399 EVB IND board has a Type-C interface DisplayPort. It use fusb302 chip as Type-C controller. fusb302 chip ---> USB/DP PHY0 <> CDN-DP controller Signed-off-by: Chaoyi Chen --- Changes in v2: - Add endpoint to link DP PHY and DP controller. - Fix devicetree codin

Re: [PATCH v3 1/5] dt-bindings: Fixup x1e80100 to add DP MST support

On 18/07/2025 01:28, Jessica Zhang wrote: > From: Abhinav Kumar > > Add x1e80100 to the dp-controller bindings, fix the > displayport-controller reg bindings, and drop > assigned-clock-parents/assigned-clocks > > Signed-off-by: Abhinav Kumar > Reviewed-by: "Rob Herring (Arm)" That's not a co

linux-next: manual merge of the drm tree with the drm-misc-fixes tree

Hi all, Today's linux-next merge of the drm tree got a conflict in: drivers/gpu/drm/virtio/virtgpu_prime.c between commit: 0ecfb8ddb953 ("Revert "drm/virtio: Use dma_buf from GEM object instance"") from the drm-misc-fixes tree and commit: 44b6535d8ace ("drm/virtio: Fix NULL pointer dere

[PATCH] drm/mediatek: Fix device/node reference count leaks in mtk_drm_get_all_drm_priv

Using device_find_child() and of_find_device_by_node() to locate devices could cause an imbalance in the device's reference count. device_find_child() and of_find_device_by_node() both call get_device() to increment the reference count of the found device before returning the pointer. In mtk_drm_ge

Re: [PATCH v4 4/7] drm/panthor: Introduce sampling sessions to handle userspace clients

On 16.05.2025 16:49, Lukas Zapolskas wrote: > To allow for combining the requests from multiple userspace clients, an > intermediary layer between the HW/FW interfaces and userspace is > created, containing the information for the counter requests and > tracking of insert and extract indices. Each

[PULL] drm-xe-fixes

Hi Dave and Sima, Here is drm-xe-fixes targeting v6.16-rc7: drm-xe-fixes-2025-07-17: Driver Changes: - SR-IOV fixes for GT reset and TLB invalidation - Fix memory copy direction during migration - Fix alignment check on migration - Fix MOCS and page fault init order to correctly account for to

Re: [PATCH v4 3/7] drm/panthor: Add panthor perf initialization and termination

On 16.05.2025 16:49, Lukas Zapolskas wrote: > Added the panthor_perf system initialization and unplug code to allow > for the handling of userspace sessions to be added in follow-up > patches. > > Signed-off-by: Lukas Zapolskas > --- > drivers/gpu/drm/panthor/panthor_device.c | 2 + > drivers/gp

Re: [PATCH v4 2/7] drm/panthor: Add DEV_QUERY.PERF_INFO handling for Gx10

On 16.05.2025 16:49, Lukas Zapolskas wrote: > This change adds the IOCTL to query data about the performance counter > setup. Some of this data was available via previous DEV_QUERY calls, > for instance for GPU info, but exposing it via PERF_INFO > minimizes the overhead of creating a single sessio

Re: [PATCH v4 1/7] drm/panthor: Add performance counter uAPI

Hi Lucas, On 16.05.2025 16:49, Lukas Zapolskas wrote: > This patch extends the DEV_QUERY ioctl to return information about the > performance counter setup for userspace, and introduces the new > ioctl DRM_PANTHOR_PERF_CONTROL in order to allow for the sampling of > performance counters. > > The ne

Re: [PATCH] Revert "drm/amd/display: limit clear_update_flags to dcn32 and above"

On 7/17/25 5:18 PM, Melissa Wen wrote: > On 17-07-2025 19:17, Matthew Schwartz wrote: >> On Thu, Jul 17, 2025 at 12:43 PM Melissa Wen wrote: >>> >>> >>> >>> On 17/07/2025 16:28, Matthew Schwartz wrote: On Thu, Jul 17, 2025 at 12:18 PM Melissa Wen wrote: > On 17-07-2025 17:57, Matthew Sch

Re: [PATCH] Revert "drm/amd/display: limit clear_update_flags to dcn32 and above"

On 17-07-2025 19:17, Matthew Schwartz wrote: > On Thu, Jul 17, 2025 at 12:43 PM Melissa Wen wrote: >> >> >> >> On 17/07/2025 16:28, Matthew Schwartz wrote: >> > On Thu, Jul 17, 2025 at 12:18 PM Melissa Wen wrote: >> >> On 17-07-2025 17:57, Matthew Schwartz wrote: >> On Jul 17, 2025, at 9:58 

Re: [PATCH v2] agp/amd64: Check AGP Capability before binding to unsupported devices

On Mon, Jul 07, 2025 at 03:58:30PM +0200, Lukas Wunner wrote: > On Mon, Jul 07, 2025 at 02:53:32PM +0200, Hans de Goede wrote: > > So I think we should move forward with Lukas' fix dor 6.16 and then > > my patch to disable probing of unsupported devices by default can > > be merged into linux-next

Re: [PATCH 6/9] drm/msm/dp: Work around bogus maximum link rate

Le jeu. 17 juil. 2025 à 23:10, Konrad Dybcio a écrit : > > On 7/17/25 10:27 PM, Jérôme de Bretagne wrote: > > On 2025/7/17 04:21, Xilin Wu wrote : > >> > >> On 2025/7/15 01:35:42, Dale Whinham wrote: > >>> From: Jérôme de Bretagne > >>> > >>> The OLED display in the Surface Pro 11 reports a maxi

Re: [PATCH 6/9] drm/msm/dp: Work around bogus maximum link rate

On 2025/7/17 04:21, Xilin Wu wrote : > > On 2025/7/15 01:35:42, Dale Whinham wrote: > > From: Jérôme de Bretagne > > > > The OLED display in the Surface Pro 11 reports a maximum link rate of > > zero in its DPCD, causing it to fail to probe correctly. > > > > The Surface Pro 11's DSDT table conta

[GIT PULL] mediatek drm fixes - 20250718

Hi, Dave & Daniel: This includes: 1. Add wait_event_timeout when disabling plane 2. only announce AFBC if really supported 3. mtk_dpi: Reorder output formats on MT8195/88 Regards, Chun-Kuang. The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494: Linux 6.16-rc1 (2025-06-

[PATCH v3 3/5] dt-bindings: display/msm: drop assigned-clock-parents for dp controller

From: Abhinav Kumar Current documentation of assigned-clock-parents for dp controller does not describe its functionality correctly making it harder to extend it for adding multiple streams. Instead of fixing up the documentation, drop the assigned-clock-parents and assigned-clocks along with th

[PATCH v3 5/5] arm64: dts: qcom: Add MST pixel streams for displayport

The following chipsets support 2 total pixel streams: - sa8775p (on mdss_dp1) - sc8180x - sc8280xp (mdss_dp0-2 only) - sm8150 - sm8350 - sm8450 - sm8650 - x1e80100 The following chipset also supports 4 total pixel streams: - sa8775p (mdss_dp0 only) Add the appropriate amount of

[PATCH v3 4/5] dt-bindings: display/msm: add stream pixel clock bindings for MST

From: Abhinav Kumar On some chipsets such as qcom,sa8775p-dp, qcom,sm8650-dp and some more, the display port controller can support more than one pixel stream (multi-stream transport). These chipsets can support up to 4 stream pixel clocks for display port controller. To support MST on these pla

[PATCH v3 2/5] dt-bindings: clock: Add SC7280 DISPCC DP pixel 1 clock binding

From: Abhinav Kumar Add DISP_CC_MDSS_DP_PIXEL1_* macros for SC7280 Signed-off-by: Abhinav Kumar Acked-by: "Rob Herring (Arm)" Signed-off-by: Jessica Zhang --- include/dt-bindings/clock/qcom,dispcc-sc7280.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/dt-bindings/clock/qcom,d

[PATCH v3 1/5] dt-bindings: Fixup x1e80100 to add DP MST support

From: Abhinav Kumar Add x1e80100 to the dp-controller bindings, fix the displayport-controller reg bindings, and drop assigned-clock-parents/assigned-clocks Signed-off-by: Abhinav Kumar Reviewed-by: "Rob Herring (Arm)" Signed-off-by: Jessica Zhang --- .../devicetree/bindings/display/msm/dp-c

[PATCH v3 0/5] dt-bindings: msm/dp: Add support for 4 pixel streams

On some MSM chipsets, the display port controller is capable of supporting up to 4 streams. To drive these additional streams, the pixel clocks for the corresponding stream needs to be enabled. Fixup the documentation of some of the bindings to clarify exactly which stream they correspond to, the

Re: [PATCH v4 2/5] PCI: Put PCIe ports with downstream devices into D3 at hibernate

On Mon, Jun 16, 2025 at 12:50:16PM -0500, Mario Limonciello wrote: > From: Mario Limonciello > > For the suspend flow PCIe ports that have downstream devices are put into > the appropriate D3 state when children are not in D0. For the hibernate > flow, PCIe ports with downstream devices stay in D

Re: [PATCH v4 2/5] PCI: Put PCIe ports with downstream devices into D3 at hibernate

Thanks for looking. On 7/17/25 4:55 PM, Bjorn Helgaas wrote: On Mon, Jun 16, 2025 at 12:50:16PM -0500, Mario Limonciello wrote: From: Mario Limonciello For the suspend flow PCIe ports that have downstream devices are put into the appropriate D3 state when children are not in D0. For the hiber

[PATCH 3/3] drm/bridge: synopsys: Do not warn about audio params computation

There is no need to warn about non pre-computed values, just change it to dbg. Signed-off-by: Detlev Casanova --- drivers/gpu/drm/bridge/synopsys/dw-hdmi-qp.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/gpu/drm/bridge/synopsys/dw-hdmi-qp.c b/drivers/gpu/drm/bri

[PATCH 2/3] ASoC: hdac_hdmi: Use dev_info on invalid ELD version

When disconnected, the ELD data cannot be read by the display driver, so it just sets the data to 0. That makes the ELD parsing code read an ELD version of 0, which is invalid. In hdac_hdmi, that is logged with dev_err(), but should be logged with dev_info() instead as it is done in sound/core/pcm

[PATCH 1/3] drm/bridge: dw-hdmi-qp: Return 0 in audio prepare when disconnected

To configure audio registers, the clock of the video port in use must be enabled. As those clocks are managed by the VOP driver, they can't be enabled here to write the registers even when the HDMI cable is disconnected. Furthermore, the registers values are computed from the TMDS char rate, which

[PATCH 0/3] Clean some logs on rockchip hdmi audio

HDMI audio is showing lots of logs, particularly when HDMI is disconnected. It doubled on RK3588 with the addition of the second HDMI TX port, so clean it up to avoid missing important log lines. Detlev Casanova (3): drm/bridge: dw-hdmi-qp: Return 0 in audio prepare when disconnected ASoC: hd

Re: [PATCH v4 2/5] PCI: Put PCIe ports with downstream devices into D3 at hibernate

On Mon, Jun 16, 2025 at 12:50:16PM -0500, Mario Limonciello wrote: > From: Mario Limonciello > > For the suspend flow PCIe ports that have downstream devices are put into > the appropriate D3 state when children are not in D0. For the hibernate > flow, PCIe ports with downstream devices stay in D

[pull] amdgpu, amdkfd, radeon drm-next-6.17

Hi Dave, Simona, One more round of updates for 6.17. The following changes since commit 7e11e01d1f1d00cb308f9351511e9597a4f70678: Merge tag 'amd-drm-next-6.17-2025-07-11' of https://gitlab.freedesktop.org/agd5f/linux into drm-next (2025-07-11 23:55:40 +0200) are available in the Git reposit

Re: [PATCH 6/9] drm/msm/dp: Work around bogus maximum link rate

On 7/17/25 10:27 PM, Jérôme de Bretagne wrote: > On 2025/7/17 04:21, Xilin Wu wrote : >> >> On 2025/7/15 01:35:42, Dale Whinham wrote: >>> From: Jérôme de Bretagne >>> >>> The OLED display in the Surface Pro 11 reports a maximum link rate of >>> zero in its DPCD, causing it to fail to probe corre

[PATCH] drm/amdgpu: check if hubbub is NULL in debugfs/amdgpu_dm_capabilities

HUBBUB structure is not initialized on DCE hardware, so check if it is NULL to avoid null dereference while accessing amdgpu_dm_capabilities file in debugfs. Signed-off-by: Peter Shkenev --- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_debugfs.c | 2 +- 1 file changed, 1 insertion(+), 1 delet

Re: [PATCH v9 0/9] Adjust fbcon console device detection

On Thu, Jul 17, 2025 at 12:38:03PM -0500, Mario Limonciello wrote: > From: Mario Limonciello > > Systems with more than one GPU userspace doesn't know which one to be > used to treat as primary. The concept of primary is important to be > able to decide which GPU is used for display and which i

[PATCH] drm/amdgpu: check if hubbub is NULL in debugfs/amdgpu_dm_capabilities

HUBBUB structure is not initialized on DCE hardware, so check if it is NULL to avoid null dereference while accessing amdgpu_dm_capabilities file in debugfs. Signed-off-by: Peter Shkenev --- drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_debugfs.c | 2 +- 1 file changed, 1 insertion(+), 1 delet

Re: [PATCH] Revert "drm/amd/display: limit clear_update_flags to dcn32 and above"

On Thu, Jul 17, 2025 at 12:43 PM Melissa Wen wrote: > > > > On 17/07/2025 16:28, Matthew Schwartz wrote: > > On Thu, Jul 17, 2025 at 12:18 PM Melissa Wen wrote: > >> On 17-07-2025 17:57, Matthew Schwartz wrote: > On Jul 17, 2025, at 9:58 AM, Limonciello, Mario > wrote: > > O

Re: Regression: DDC I2C Display Freezing for internal displays

Hi, just tested that this Bug still exists in kernel version 6.16-rc6. The example trigger from my previous mail still works triggering screen freezing shortly after invocation. I also learned that setting kernel param `amdgpu.dcdebugmask=0x10` works as a workaround. Kind regards, Felix Ri

Re: [PATCH] Revert "drm/amd/display: limit clear_update_flags to dcn32 and above"

On 17/07/2025 16:28, Matthew Schwartz wrote: On Thu, Jul 17, 2025 at 12:18 PM Melissa Wen wrote: On 17-07-2025 17:57, Matthew Schwartz wrote: On Jul 17, 2025, at 9:58 AM, Limonciello, Mario wrote: On 7/17/25 11:55 AM, Melissa Wen wrote: On 17-07-2025 13:39, Limonciello, Mario wrote: On

Re: [PATCH] Revert "drm/amd/display: limit clear_update_flags to dcn32 and above"

On Thu, Jul 17, 2025 at 12:18 PM Melissa Wen wrote: > > On 17-07-2025 17:57, Matthew Schwartz wrote: > >> On Jul 17, 2025, at 9:58 AM, Limonciello, Mario > >> wrote: > >> > >> On 7/17/25 11:55 AM, Melissa Wen wrote: > >>> On 17-07-2025 13:39, Limonciello, Mario wrote: > On 7/17/25 9:36 AM,

Re: [PATCH] Revert "drm/amd/display: limit clear_update_flags to dcn32 and above"

On 17-07-2025 17:57, Matthew Schwartz wrote: >> On Jul 17, 2025, at 9:58 AM, Limonciello, Mario >> wrote: >> >> On 7/17/25 11:55 AM, Melissa Wen wrote: >>> On 17-07-2025 13:39, Limonciello, Mario wrote: On 7/17/25 9:36 AM, Melissa Wen wrote: > This reverts commit e1bd5e0bb4ca0d633ad698a

Re: [PATCH] Revert "drm/amd/display: limit clear_update_flags to dcn32 and above"

On 7/17/25 1:57 PM, Matthew Schwartz wrote: > > >> On Jul 17, 2025, at 9:58 AM, Limonciello, Mario >> wrote: >> >> On 7/17/25 11:55 AM, Melissa Wen wrote: >>> On 17-07-2025 13:39, Limonciello, Mario wrote: On 7/17/25 9:36 AM, Melissa Wen wrote: > This reverts commit e1bd5e0bb4ca0d633ad

[PATCH 3/4] ARM: dts: sti: extract display subsystem out of soc

The display subsystem represent how IPs are interacting together and have nothing to do within the SoC node. Extract it from the SoC node and let IPs nodes in the Soc node. Several nodes did not use conventional name: * sti-display-subsystem -> display-subsystem * sti-controller -> display-cont

[PATCH 4/4] ARM: dts: sti: remove useless cells fields

tvout node do not need the cells fields. Remove them. Signed-off-by: Raphael Gallais-Pou --- arch/arm/boot/dts/st/stih410.dtsi | 2 -- 1 file changed, 2 deletions(-) diff --git a/arch/arm/boot/dts/st/stih410.dtsi b/arch/arm/boot/dts/st/stih410.dtsi index 47d66d7eb07a3d73d98b3e21d62b2253aa1171

[PATCH 2/4] drm/sti: make use of drm_of_component_probe

Enhance the probing sequence by using the ports property of the display-subsystem node. That done, it becomes possible to handle the display-substem node outside of the soc node within the device-tree and not have each IP blocks as children of the display-subsystem node. Signed-off-by: Raphael Ga

[PATCH 1/4] drm/sti: check dma_set_coherent_mask return value

Return value for DMA allocation was not checked. Check it and return error code in case of failing. Signed-off-by: Raphael Gallais-Pou --- drivers/gpu/drm/sti/sti_drv.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/sti/sti_drv.c b/drivers/gpu/drm/sti/st

[PATCH 0/4] STi device-tree display subsystem rework

This serie aims to rework the display-subsystem node, which was previously included directly within the SoC node. This was wrong because it is an abstraction and describes how IPs behave together, not what the hardware is. Instead, extract display-subsystem outside of the SoC node, and let IPs de

Re: [PATCH v3 1/2] drm: Add DRM prime interface to reassign GEM handle

On 2025-07-17 10:35, David Francis wrote: > CRIU restore of drm buffer objects requires the ability to create > or import a buffer object with a specific gem handle. > > Add new drm ioctl DRM_IOCTL_GEM_CHANGE_HANDLE, which takes > the gem handle of an object and moves that object to a > specified n

Re: [PATCH] Revert "drm/amd/display: limit clear_update_flags to dcn32 and above"

On 17-07-2025 15:58, Limonciello, Mario wrote: > On 7/17/25 11:55 AM, Melissa Wen wrote: >> On 17-07-2025 13:39, Limonciello, Mario wrote: >>> On 7/17/25 9:36 AM, Melissa Wen wrote: This reverts commit e1bd5e0bb4ca0d633ad698abd3658f8265009b81. The commit causes a regression in Steam

Re: [PATCH v4 3/5] drm/amd: Avoid evicting resources at S5

On Mon, Jun 16, 2025 at 1:50 PM Mario Limonciello wrote: > > From: Mario Limonciello > > Normally resources are evicted on dGPUs at suspend or hibernate and > on APUs at hibernate. These steps are unnecessary when using the S4 > callbacks to put the system into S5. > > Cc: AceLan Kao > Cc: Kai-

Re: [PATCH] Revert "drm/amd/display: limit clear_update_flags to dcn32 and above"

> On Jul 17, 2025, at 9:58 AM, Limonciello, Mario > wrote: > > On 7/17/25 11:55 AM, Melissa Wen wrote: >> On 17-07-2025 13:39, Limonciello, Mario wrote: >>> On 7/17/25 9:36 AM, Melissa Wen wrote: This reverts commit e1bd5e0bb4ca0d633ad698abd3658f8265009b81. The commit causes a

Re: [PATCH v3 0/4] drm: Fix bug in panel driver, update MIPI support macros

Woops. When I copied over the subject from the previous cover letter, I accidentally overwrote v4 with v3. I'll issue a v5 if that's a problem. My bad, Brigham

Re: [PULL] drm-intel-fixes

On Thu, Jul 17, 2025 at 11:02:49AM -0400, Rodrigo Vivi wrote: > Hi Dave and Sima, > > Here goes the drm-intel-fixes of this week > with a single display fix. > > This might conflict when getting merged, but the > solution is trivial to go what is already in the -next trees. doh! it looks that I

[PATCH v9 9/9] PCI: Add a new 'boot_display' attribute

From: Mario Limonciello On systems with multiple GPUs there can be uncertainty which GPU is the primary one used to drive the display at bootup. In some desktop environments this can lead to increased power consumption because secondary GPUs may be used for rendering and never go to a low power s

[PATCH v9 6/9] Fix access to video_is_primary_device() when compiled without CONFIG_VIDEO

From: Mario Limonciello When compiled without CONFIG_VIDEO the architecture specific implementations of video_is_primary_device() include prototypes and assume that video-common.c will be linked. Guard against this so that the fallback inline implementation that returns false will be used when co

[PATCH v9 8/9] fbcon: Use screen info to find primary device

From: Mario Limonciello On systems with non VGA GPUs fbcon can't find the primary GPU because video_is_primary_device() only checks the VGA arbiter. Add a screen info check to video_is_primary_device() so that callers can get accurate data on such systems. Reviewed-by: Thomas Zimmermann Sugges

[PATCH v9 7/9] PCI/VGA: Replace vga_is_firmware_default() with a screen info check

From: Mario Limonciello vga_is_firmware_default() checks firmware resources to find the owner framebuffer resources to find the firmware PCI device. This is an open coded implementation of screen_info_pci_dev(). Switch to using screen_info_pci_dev() instead. Acked-by: Bjorn Helgaas Suggested-

[PATCH v9 5/9] ALSA: hda: Use pci_is_display()

From: Mario Limonciello The inline pci_is_display() helper does the same thing. Use it. Reviewed-by: Takashi Iwai Reviewed-by: Daniel Dadap Reviewed-by: Simona Vetter Suggested-by: Bjorn Helgaas Signed-off-by: Mario Limonciello --- sound/hda/hdac_i915.c | 2 +- sound/pci/hda/hda_intel

[PATCH v9 3/9] vga_switcheroo: Use pci_is_display()

From: Mario Limonciello The inline pci_is_display() helper does the same thing. Use it. Reviewed-by: Daniel Dadap Reviewed-by: Simona Vetter Suggested-by: Bjorn Helgaas Signed-off-by: Mario Limonciello --- drivers/gpu/vga/vga_switcheroo.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(

[PATCH v9 4/9] iommu/vt-d: Use pci_is_display()

From: Mario Limonciello The inline pci_is_display() helper does the same thing. Use it. Reviewed-by: Lu Baolu Reviewed-by: Daniel Dadap Reviewed-by: Simona Vetter Suggested-by: Bjorn Helgaas Signed-off-by: Mario Limonciello --- drivers/iommu/intel/iommu.c | 2 +- 1 file changed, 1 inserti

[PATCH v9 2/9] vfio/pci: Use pci_is_display()

From: Mario Limonciello The inline pci_is_display() helper does the same thing. Use it. Acked-by: Alex Williamson Reviewed-by: Daniel Dadap Reviewed-by: Simona Vetter Suggested-by: Bjorn Helgaas Signed-off-by: Mario Limonciello --- drivers/vfio/pci/vfio_pci_igd.c | 3 +-- 1 file changed,

[PATCH v9 0/9] Adjust fbcon console device detection

From: Mario Limonciello Systems with more than one GPU userspace doesn't know which one to be used to treat as primary. The concept of primary is important to be able to decide which GPU is used for display and which is used for rendering. If it's guessed wrong then both GPUs will be kept awak

[PATCH v9 1/9] PCI: Add helper for checking if a PCI device is a display controller

From: Mario Limonciello Several places in the kernel do class shifting to match whether a PCI device is display class. Introduce a helper for those places to use. Acked-by: Bjorn Helgaas Reviewed-by: Daniel Dadap Reviewed-by: Simona Vetter Signed-off-by: Mario Limonciello --- include/linux

[pull] radeon, amdgpu drm-fixes-6.16

Hi Dave, Simona, Fixes for 6.16. The following changes since commit 347e9f5043c89695b01e66b3ed111755afcf1911: Linux 6.16-rc6 (2025-07-13 14:25:58 -0700) are available in the Git repository at: https://gitlab.freedesktop.org/agd5f/linux.git tags/amd-drm-fixes-6.16-2025-07-17 for you to fe

Re: [PATCH] Revert "drm/amd/display: limit clear_update_flags to dcn32 and above"

On 17-07-2025 15:55, Melissa Wen wrote: > On 17-07-2025 13:39, Limonciello, Mario wrote: >> On 7/17/25 9:36 AM, Melissa Wen wrote: >>> This reverts commit e1bd5e0bb4ca0d633ad698abd3658f8265009b81. >>> >>> The commit causes a regression in Steam Deck (DCN 3.01), reintroducing a >>> functional issue

Re: [PATCH] Revert "drm/amd/display: limit clear_update_flags to dcn32 and above"

On 7/17/25 11:55 AM, Melissa Wen wrote: > On 17-07-2025 13:39, Limonciello, Mario wrote: >> On 7/17/25 9:36 AM, Melissa Wen wrote: >>> This reverts commit e1bd5e0bb4ca0d633ad698abd3658f8265009b81. >>> >>> The commit causes a regression in Steam Deck (DCN 3.01), reintroducing a >>> functional issue

Re: [PATCH] Revert "drm/amd/display: limit clear_update_flags to dcn32 and above"

On 17-07-2025 13:39, Limonciello, Mario wrote: > On 7/17/25 9:36 AM, Melissa Wen wrote: >> This reverts commit e1bd5e0bb4ca0d633ad698abd3658f8265009b81. >> >> The commit causes a regression in Steam Deck (DCN 3.01), reintroducing a >> functional issue reported in [1] that was fixed by calling the

Re: [PATCH v5 00/16] drm/vkms: Add configfs support

Merged into Android tree: https://android-review.git.corp.google.com/c/kernel/common-modules/virtual-device/+/3661920 I'm able to use configfs as expected. Tested-by: Mark Yacoub On Thu, Jul 17, 2025 at 12:37 PM Louis Chauvet wrote: > > +CC: Mark (Google), Sebastian (Mutter), Xaver (KWin), Vic

Re: [PATCH v5 00/16] drm/vkms: Add configfs support

Merged into Android tree: https://android-review.git.corp.google.com/c/kernel/common-modules/virtual-device/+/3661920 I'm able to use configfs as expected. Tested-by: Mark Yacoub On Thu, Jul 17, 2025 at 12:37 PM Louis Chauvet wrote: > +CC: Mark (Google), Sebastian (Mutter), Xaver (KWin), Victo

[PATCH v4 4/4] drm: docs: Update task from drm TODO list

Update TODO item from drm documentation to contain more applicable information regarding the removal of deprecated MIPI DSI functions and no longer reference functions which have already been removed from the kernel. Reviewed-by: Douglas Anderson Signed-off-by: Brigham Campbell --- Documentatio

[PATCH v4 2/4] drm/panel: jdi-lpm102a188a: Fix bug and clean up driver

Fix bug in unprepare() which causes the function's return value to be that of the last mipi "enter sleep mode" command. Update driver to use the "multi" variant of MIPI functions in order to facilitate improved error handling and remove the panel's dependency on deprecated MIPI functions. Use the

[PATCH v4 3/4] drm: Remove unused MIPI write seq and chatty functions

Remove the deprecated mipi_dsi_generic_write_seq() and mipi_dsi_generic_write_chatty() functions now that they are no longer used. Reviewed-by: Douglas Anderson Signed-off-by: Brigham Campbell --- drivers/gpu/drm/drm_mipi_dsi.c | 34 +++--- include/drm/drm_mipi_dsi.h

[PATCH v4 1/4] drm: Create mipi_dsi_dual macro

Create mipi_dsi_dual macro for panels which are driven by two parallel serial interfaces. This allows for the reduction of code duplication in drivers for these panels. Signed-off-by: Brigham Campbell --- include/drm/drm_mipi_dsi.h | 24 1 file changed, 24 insertions(+)

[PATCH v3 0/4] drm: Fix bug in panel driver, update MIPI support macros

This series removes the unintuitive mipi_dsi_generic_write_seq() macro and related mipi_dsi_generic_write_chatty() method from the drm subsystem. This is in accordance with a TODO item from Douglas Anderson in the drm subsystem documentation. Tejas Vipin (among others) has largely spearheaded this

Re: [PATCH v2] drm: document DRM_MODE_PAGE_FLIP_EVENT interactions with atomic

Thanks for the review Simona!

Re: [PATCH v5 00/16] drm/vkms: Add configfs support

+CC: Mark (Google), Sebastian (Mutter), Xaver (KWin), Victoria (Cosmic) Hi everyone, Last week, I presented this work at the Display Next Hackfest, and the feedback from compositors was very positive. At least KWin, Mutter, and Cosmic are interested in integrating it into their tests, so it wo

Re: [PATCH v4 3/3] drm/tidss: oldi: Add atomic_check hook for oldi bridge

Hi, On 04/07/2025 12:48, Jayesh Choudhary wrote: > Since OLDI consumes DSS VP clock directly as serial clock, certain I don't think that's true. Although depends what you mean with VP clock. I think VP clock is whatever pclk goes into the DSS. OLDI gets a serial clock from the PLL. That same clo

Re: [PATCH v4 2/3] drm/tidss: Remove max_pclk_khz from tidss display features

Hi, On 04/07/2025 12:48, Jayesh Choudhary wrote: > TIDSS hardware by itself does not have variable max_pclk for each VP. > The maximum pixel clock is determined by the limiting factor between > the functional clock and the PLL (parent to the VP/pixel clock). I'm sorry, what does that mean? "limit

Re: [PATCH v4 1/3] drm/tidss: oldi: Add property to identify OLDI supported VP

Hi, On 04/07/2025 12:48, Jayesh Choudhary wrote: > TIDSS should know which VP has OLDI output to avoid calling clock > functions for that VP as those are controlled by oldi driver. Add a "OLDI" > property "is_oldi_vp" to "tidss_device" structure for that. Mark it > 'true' in tidss_oldi_init() an

Re: [PATCH v2 02/10] clk: imx95-blk-ctl: Save/restore registers when RPM routines are called

On Thu, Jul 17, 2025 at 03:23:38PM +0300, Laurentiu Palcu wrote: > Hi Frank, > > On Wed, Jul 16, 2025 at 02:29:01PM -0400, Frank Li wrote: > > On Wed, Jul 16, 2025 at 11:15:06AM +0300, Laurentiu Palcu wrote: > > > If runtime PM is used for the clock providers and they're part of a > > > power domai

Re: [PATCH] drm/amdgpu: Raven: don't allow mixing GTT and VRAM

On 17.07.25 16:58, Alex Deucher wrote: > On Wed, Jul 16, 2025 at 8:13 PM Brian Geffon wrote: >> On Wed, Jul 16, 2025 at 5:03 PM Alex Deucher wrote: >>> On Wed, Jul 16, 2025 at 12:40 PM Brian Geffon wrote: On Wed, Jul 16, 2025 at 12:33 PM Alex Deucher wrote: > On Wed, Jul 16, 2025

Re: [PATCH v2 3/3] panthor: dump task pid and comm on gpu errors

On 13/07/2025 04:08, Chia-I Wu wrote: > It is useful to know which tasks cause gpu errors. > > Signed-off-by: Chia-I Wu Reviewed-by: Steven Price > --- > drivers/gpu/drm/panthor/panthor_sched.c | 24 +++- > 1 file changed, 19 insertions(+), 5 deletions(-) > > diff --git a

Re: [PATCH v2 2/3] panthor: save task pid and comm in panthor_group

On 13/07/2025 04:08, Chia-I Wu wrote: > We would like to report them on gpu errors. > > We choose to save the info on panthor_group_create rather than on > panthor_open because, when the two differ, we are more interested in the > task that created the group. > > Signed-off-by: Chia-I Wu One ni

[PATCH] drm/msm: Fix pagetables setup/teardown serialization

An atomic counter is not sufficient, as one task could still be in the process of tearing things down while another task increments the counter back up to one and begins setup again. The race condition existed since commit b145c6e65eb0 ("drm/msm: Add support to create a local pagetable") but got b

Re: [PATCH v7 4/4] misc: fastrpc: add support for gdsp remoteproc

On Thu, Jul 17, 2025 at 10:28:44AM +0800, Ling Xu wrote: > 在 7/17/2025 3:31 AM, Bjorn Andersson 写道: > > On Mon, Jul 14, 2025 at 11:11:33AM +0530, Ling Xu wrote: > >> Some platforms (like sa8775p) feature one or more GPDSPs (General > >> Purpose DSPs). Similar to other kinds of Hexagon DSPs, they pr

[PATCH] drm/msm: Drop unneeded NULL check

This is always set in msm_gpu_init(), and can never be NULL. Reported-by: Dan Carpenter Signed-off-by: Rob Clark --- drivers/gpu/drm/msm/msm_iommu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/msm/msm_iommu.c b/drivers/gpu/drm/msm/msm_iommu.c index 55c29f

DRM GUD driver debug logging

Hello I was taking a look at the code for the gud driver. I am aware this driver was recently orphaned and I wish to get up to speed on it, and maybe with enough learning and work I can take over maintainance of it in the future. I noticed that in the function gud_disconnect in gud_driv.c on like

[PULL] drm-intel-fixes

Hi Dave and Sima, Here goes the drm-intel-fixes of this week with a single display fix. This might conflict when getting merged, but the solution is trivial to go what is already in the -next trees. Thanks, Rodrigo. drm-intel-fixes-2025-07-17: - DP AUX DPCD address fix (Imre) The following chan

Re: [PATCH] drm/amdgpu: Raven: don't allow mixing GTT and VRAM

On Wed, Jul 16, 2025 at 8:13 PM Brian Geffon wrote: > > On Wed, Jul 16, 2025 at 5:03 PM Alex Deucher wrote: > > > > On Wed, Jul 16, 2025 at 12:40 PM Brian Geffon wrote: > > > > > > On Wed, Jul 16, 2025 at 12:33 PM Alex Deucher > > > wrote: > > > > > > > > On Wed, Jul 16, 2025 at 12:18 PM Brian

Re: [RFC 0/4] Add Format Modifiers for NVIDIA Blackwell chipsets

On Wed, Jul 16, 2025 at 6:36 PM James Jones wrote: > On 7/4/25 07:45, Faith Ekstrand wrote: > > On Thu, Jul 3, 2025 at 6:34 PM James Jones > > wrote: > > > > The layout of bits within the individual tiles (referred to as > > sectors in the DRM_FORMAT_MOD_NVIDIA

Re: [PATCH] Revert "drm/amd/display: limit clear_update_flags to dcn32 and above"

On 7/17/25 9:36 AM, Melissa Wen wrote: > This reverts commit e1bd5e0bb4ca0d633ad698abd3658f8265009b81. > > The commit causes a regression in Steam Deck (DCN 3.01), reintroducing a > functional issue reported in [1] that was fixed by calling the > clear_update_flags() from commit 7671f62c10f2a. >

[PATCH] Revert "drm/amd/display: limit clear_update_flags to dcn32 and above"

This reverts commit e1bd5e0bb4ca0d633ad698abd3658f8265009b81. The commit causes a regression in Steam Deck (DCN 3.01), reintroducing a functional issue reported in [1] that was fixed by calling the clear_update_flags() from commit 7671f62c10f2a. On Steam Deck, we use multiple hw plane color caps

[PATCH v3 2/2] drm: Move drm_gem ioctl kerneldoc to uapi file

The drm_gem ioctls were documented in internal file drm_gem.c instead of uapi header drm.h. Move them there and change to appropriate kerneldoc formatting. Signed-off-by: David Francis --- drivers/gpu/drm/drm_gem.c | 30 - include/uapi/drm/drm.h| 40 ++

[PATCH v3 1/2] drm: Add DRM prime interface to reassign GEM handle

CRIU restore of drm buffer objects requires the ability to create or import a buffer object with a specific gem handle. Add new drm ioctl DRM_IOCTL_GEM_CHANGE_HANDLE, which takes the gem handle of an object and moves that object to a specified new gem handle. This ioctl needs to call drm_prime_re

  1   2   >