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

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 domain, then the power domain supply will be cut off when runtime > > suspended.

Re: [PATCH] drm/panfrost: Fix leak when free gem object

> obj->mappings.lock should be destroyed when free > panfrost gem object in panfrost_gem_free_object. How do you think about to add any tags (like “Fixes” and “Cc”) accordingly? See also: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patc

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

Hi Brigham, thanks for the patch! The code looks a lot cleaner. Some review follows. On 7/17/25 7:57 AM, Brigham Campbell wrote: 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 MI

Re: [PATCH 0/2] drm/v3d: Expose global and per-context GPU reset counters

On Fri, 11 Jul 2025 12:18:30 -0300, Maíra Canal wrote: > The GL extension KHR_robustness requires a mechanism for a GL application > to learn about graphics resets that affect a GL context. With the goal > to provide support for such extension in Mesa, this series implements > global and per-cont

[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

[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 ++

Add CHANGE_HANDLE ioctl for drm gem v3

This patch adds a new ioctl GEM_CHANGE_HANDLE which is needed by amdgpu CRIU for dmabuf. The ioctl allows a user to move a gem object to a new handle. v2: Move documentation for this and other drm_gem ioctls to drm.h v3: After testing with IGT, fixed return value on success Accompanying changes:

[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

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. >

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

[PATCH v1 2/5] clk: tegra20: reparent dsi clock to pll_d_out0

Reparent DSI clock to PLLD_OUT0 instead of directly descend from PLLD. Signed-off-by: Svyatoslav Ryhel --- drivers/clk/tegra/clk-tegra20.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/clk/tegra/clk-tegra20.c b/drivers/clk/tegra/clk-tegra20.c index 2c58ce25af75

[PATCH v1 1/5] dt-bindings: display: tegra: document MIPI calibration for Tegra20/Tegra30

Adjust Tegra114 MIPI calibration schema to include Tegra20/Tegra30 MIPI calibration logic. Signed-off-by: Svyatoslav Ryhel --- .../display/tegra/nvidia,tegra114-mipi.yaml | 41 --- 1 file changed, 36 insertions(+), 5 deletions(-) diff --git a/Documentation/devicetree/bindings

[PATCH v1 0/5] gpu/drm: tegra: add DSI support for Tegra20/Tegra30

Tegra20/Tegra30 DSI is quite similar to Tegra114+ apart MIPI calibration logic and clocks. With a few minor tweaks, existing tegra DSI driver should work on Tegra20/Tegra30 devices just fine. Tested on Motorola Atrix 4G (T20) and ASUS VivoTab RT TF600T (T30). Svyatoslav Ryhel (5): dt-bindings: d

[PATCH v1 4/5] gpu/drm: tegra: dsi: add support for Tegra20/Tegra30

Tegra20/Tegra30 are fully compatible with existing tegra DSI driver apart clock configuration and MIPI calibration which are addressed by this patch. Signed-off-by: Svyatoslav Ryhel --- drivers/gpu/drm/tegra/drm.c | 2 ++ drivers/gpu/drm/tegra/dsi.c | 69 ++--- d

[PATCH v1 5/5] ARM: tegra: add MIPI calibration binding for Tegra20/Tegra30

Add MIPI calibration device node for Tegra20 and Tegra30. Signed-off-by: Svyatoslav Ryhel --- arch/arm/boot/dts/nvidia/tegra20.dtsi | 14 ++ arch/arm/boot/dts/nvidia/tegra30.dtsi | 18 ++ 2 files changed, 32 insertions(+) diff --git a/arch/arm/boot/dts/nvidia/tegra20

[PATCH v1 3/5] gpu/drm: host1x: mipi: add Tegra20/Tegra30 MIPI calibration logic

Tegra20/Tegra30 have no dedicated MIPI calibration device and calibration registers are incorporated into CSI. Lets reuse Tegra114 calibration framework and add Tegra20/Tegra30 as a special case. Signed-off-by: Svyatoslav Ryhel --- drivers/gpu/host1x/mipi.c | 82 +

[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 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

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] 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 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 v2] drm: document DRM_MODE_PAGE_FLIP_EVENT interactions with atomic

Thanks for the review Simona!

[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 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 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

[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 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] 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

[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

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

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] 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 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 v2 2/2] rust: types: rename Opaque::raw_get to cast_into

On Tue, Jun 24, 2025 at 5:28 PM Alice Ryhl wrote: > > -let cell_inner = ::core::cell::UnsafeCell::raw_get(self_ptr); > +let cell_inner = > ::core::cell::UnsafeCell::cast_into(self_ptr); Bah, we also missed this one -- I will rebase / send a patch. Cheers, Miguel

Re: [PATCH v4 17/17] drm/bridge: cdns-dsi: Don't fail on MIPI_DSI_MODE_VIDEO_BURST

Hi Tomi, On 17/07/25 15:59, Tomi Valkeinen wrote: Hi, On 17/07/2025 12:36, Devarsh Thakkar wrote: Hi Tomi Thanks for the patch. On 18/06/25 15:29, Tomi Valkeinen wrote: While the cdns-dsi does not support DSI burst mode, the burst mode is essentially DSI event mode with more versatile clock

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 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 v2 07/10] drm/imx: Add support for i.MX94 DCIF

Hi Frank, On Wed, Jul 16, 2025 at 02:58:34PM -0400, Frank Li wrote: > On Wed, Jul 16, 2025 at 11:15:11AM +0300, Laurentiu Palcu wrote: > > From: Sandor Yu > > > > The i.MX94 Display Control Interface features: > > * Up to maximum 3 layers of alpha blending: > > - 1 background layer(Layer 0);

Re: [PATCH] drm/tidss: encoder: convert to devm_drm_bridge_alloc()

Hello Jyri, Tomi, Michael, On Thu, 17 Jul 2025 09:49:44 +0200 "Michael Walle" wrote: > Hi, > > thanks for taking a look! > > > However allocating an encoder using a bridge alloc function (while we > > used to call an encoder allocation function) looks counter-intuitive. > > > > We had discusse

[PATCH v1 1/2] dt-bindings: display: panel: Document Hydis HV101HD1 DSI panel

Hydis HV101HD1 is a 2-lane 1366x768 MIPI DSI panel found in ASUS VivoTab RT TF600T tablet. Signed-off-by: Svyatoslav Ryhel --- .../display/panel/hydis,hv101hd1.yaml | 60 +++ 1 file changed, 60 insertions(+) create mode 100644 Documentation/devicetree/bindings/display/p

[PATCH v1 2/2] drm: panel: Add support for Hydis HV101HD1 MIPI DSI panel

HV101HD1-1E1 is a color active matrix TFT LCD module using amorphous silicon TFT's (Thin Film Transistors) as an active switching devices. This module has a 10.1 inch diagonally measured active area with HD resolutions (1366 horizontal by 768 vertical pixel array). Signed-off-by: Svyatoslav Ryhel

[PATCH v1 0/2] drm: panel: add support for panel used in ASUS VivoTab RT TF600T

Add support for Hydis HV101HD1 MIPI DSI panel used in ASUS VivoTab RT TF600T. Svyatoslav Ryhel (2): dt-bindings: display: panel: Document Hydis HV101HD1 DSI panel drm: panel: Add support for Hydis HV101HD1 MIPI DSI panel .../display/panel/hydis,hv101hd1.yaml | 60 ++ drivers/gpu

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

[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

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

[PATCH v6 1/2] drm/rockchip: inno-hdmi: Convert to drm bridge

From: Andy Yan Convert it to drm bridge driver, it will be convenient for us to migrate the connector part to the display driver later. Signed-off-by: Andy Yan --- Changes in v6: - Rebase on latest drm-misc-next - Link to V5: https://lore.kernel.org/linux-rockchip/20250512124615.2848731-1-an

[PATCH v2] drm/sched: Remove optimization that causes hang when killing dependent jobs

When application A submits jobs and application B submits a job with a dependency on A's fence, the normal flow wakes up the scheduler after processing each job. However, the optimization in drm_sched_entity_add_dependency_cb() uses a callback that only clears dependencies without waking up the sch

Re: [RFC PATCH 1/1] drm/i915/display: Avoid unsupported 300Hz output mode on a TUXEDO device

Am 17.07.25 um 09:30 schrieb Murthy, Arun R: -Original Message- From: Intel-gfx On Behalf Of Werner Sembach Sent: Saturday, July 5, 2025 12:34 AM To: Jani Nikula ; Vivi, Rodrigo ; Joonas Lahtinen ; Tvrtko Ursulin ; David Airlie ; Simona Vetter Cc: Tim Guttzeit ; Werner Sembach

Re: [PATCH] drm/tidss: encoder: convert to devm_drm_bridge_alloc()

Hi, thanks for taking a look! > However allocating an encoder using a bridge alloc function (while we > used to call an encoder allocation function) looks counter-intuitive. > > We had discussed on IRC a different idea, adding a wrapper structure > around the bridge. Quoting your proposal: > >

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

On 17.07.25 02:12, 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 Geffon wrote: > > Commit

Re: [PATCH v3] virtio: Update kerneldoc in drivers/virtio/virtio_dma_buf.c

> > diff --git a/drivers/virtio/virtio_dma_buf.c > > b/drivers/virtio/virtio_dma_buf.c > > index 3fe1d03b0645..986cc73c503f 100644 > > --- a/drivers/virtio/virtio_dma_buf.c > > +++ b/drivers/virtio/virtio_dma_buf.c > > @@ -16,6 +16,8 @@ > > * This wraps dma_buf_export() to allow virtio drivers t

Re: [RFC PATCH 1/1] drm/i915/display: Avoid unsupported 300Hz output mode on a TUXEDO device

-Original Message- From: Intel-gfx On Behalf Of Werner Sembach Sent: Saturday, July 5, 2025 12:34 AM To: Jani Nikula ; Vivi, Rodrigo ; Joonas Lahtinen ; Tvrtko Ursulin ; David Airlie ; Simona Vetter Cc: Tim Guttzeit ; Werner Sembach ; intel-...@lists.freedesktop.org; intel- x...@lists

Re: [PATCH] drm/tidss: encoder: convert to devm_drm_bridge_alloc()

Hello Michael, On Wed, 16 Jul 2025 15:41:07 +0200 Michael Walle wrote: > Convert the tidss encoder to use devm_drm_bridge_alloc(). Instead of > allocating the memory by drmm_simple_encoder_alloc() use > devm_drm_bridge_alloc() and initialize the encoder afterwards. > > Fixes: a7748dd127ea ("drm

[PULL] drm-misc-next

Hi Dave, Sima, An extra drm-misc-next PR this time around because I've been asked to make an exception to get the hibernation fixes for amdgpu in. This will definitely be the last PR for 6.17 :) Thanks, Maxime drm-misc-next-2025-07-17: drm-misc-next for 6.17: UAPI Changes: Cross-subsystem Cha

[PATCH v6 2/2] MAINTAINERS: Add entry for Innosilicon hdmi bridge library

From: Andy Yan Add entry for Innosilicon hdmi bridge library Signed-off-by: Andy Yan --- (no changes since v5) Changes in v5: - First included in this version MAINTAINERS | 8 1 file changed, 8 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index d97e091b1742f..f944acf7923a

[PATCH v3] Documentation: dma-buf: heaps: Add naming guidelines

We've discussed a number of times of how some heap names are bad, but not really what makes a good heap name. Let's document what we expect the heap names to look like. Reviewed-by: Bagas Sanjaya Signed-off-by: Maxime Ripard --- Changes in v3: - Grammar, spelling fixes - Remove the cacheable /

[PATCH v6 0/2] Convert inno hdmi to drm bridge

From: Andy Yan Convert it to drm bridge driver, it will be convenient for us to migrate the connector part to the display driver later. Patches that have already been merged in drm-misc-next are dropped. Changes in v6: - Rebase on latest drm-misc-next - Link to V5: https://lore.kernel.org/li

Re: [PATCH v4 17/17] drm/bridge: cdns-dsi: Don't fail on MIPI_DSI_MODE_VIDEO_BURST

Hi Tomi Thanks for the patch. On 18/06/25 15:29, Tomi Valkeinen wrote: While the cdns-dsi does not support DSI burst mode, the burst mode is essentially DSI event mode with more versatile clocking and timings. I don't fully agree with this statement, DSI burst mode and DSI event mode are two d

Re: [PATCH] drm/sched: Fix a race in DRM_GPU_SCHED_STAT_NO_HANG test

On Wed, 2025-07-16 at 09:48 +0100, Tvrtko Ursulin wrote: > The "skip reset" test waits for the timeout handler to run for the > duration of 2 * MOCK_TIMEOUT, and because the mock scheduler opted to > remove the "skip reset" flag once it fires, this gives opportunity > for the > timeout handler to r

Re: [PATCH drm-next] drm/bochs: Add support for drm_panic

On 16/07/2025 23:48, Askar Safin wrote: On Wed, 16 Jul 2025 02:00:56 +0400 Jocelyn Falempe wrote --- > Yes, that's the default if you use a drm driver like bochs with fbdev Thank you for answer! I just tried kernel from drm-tip with this config with drm_panic in qemu. And panic work

Re: [PATCH v2] drm/sched: Remove optimization that causes hang when killing dependent jobs

On Thu, 2025-07-17 at 16:44 +0800, Lin.Cao wrote: > When application A submits jobs and application B submits a job with > a > dependency on A's fence, the normal flow wakes up the scheduler after > processing each job. However, the optimization in > drm_sched_entity_add_dependency_cb() uses a call

Re: [PATCH] drm/sched: Consolidate drm_sched_job_timedout

On Wed Jul 16, 2025 at 4:48 PM CEST, Tvrtko Ursulin wrote: > Reduce to one spin_unlock for hopefully a little bit clearer flow in the > function. It may appear that there is a behavioural change with the > drm_sched_start_timeout_unlocked() now not being called if there were > initially no jobs on

Re: [PATCH] drm/panfrost: Fix leak when free gem object

On 10/07/2025 04:05, lihongtao wrote: > obj->mappings.lock should be destroyed when free > panfrost gem object in panfrost_gem_free_object. mutex_destroy() doesn't actually release any resources. It is purely a debugging feature (if CONFIG_DEBUG_MUTEXES is disabled then it is compiled away complet

Re: [PATCH v4 17/17] drm/bridge: cdns-dsi: Don't fail on MIPI_DSI_MODE_VIDEO_BURST

Hi, On 17/07/2025 12:36, Devarsh Thakkar wrote: > Hi Tomi > > Thanks for the patch. > > On 18/06/25 15:29, Tomi Valkeinen wrote: >> While the cdns-dsi does not support DSI burst mode, the burst mode is >> essentially DSI event mode with more versatile clocking and timings. > I don't fully agree

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

[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] 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: [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: [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: [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

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 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 

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 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 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 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

[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 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

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

[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 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 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: 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

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] 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

[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 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 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 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

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

[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] 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

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 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

  1   2   >