drivers/gpu/drm/rockchip/rockchip_vop2_reg.c | 46 +++++++++++++--------------- 1 file changed, 22 insertions(+), 24 deletions(-)
On RK3588/RK3568 boards with multiple active display outputs, start/stop
transitions may trigger a timeout during overlay layer configuration:
rockchip-drm display-subsystem: [drm] *ERROR* wait layer cfg done timeout
The shared OVL_LAYER_SEL and OVL_PORT_SEL shadow registers are committed
to the active configuration at the vsync of whichever Video Port is
selected by LAYERSEL_REGDONE_SEL. When two Video Ports race through
atomic commits, rk3568_vop2_setup_layer_mixer() has two issues that
cause the wait to poll for a value the hardware might not be able to
produce.
Patch 1 fixes passing the wrong target to the wait function, since the
expected value was already overwritten with the current VP's new
layer_sel before reaching the wait.
Patch 2 moves the wait before the LAYERSEL_REGDONE_SEL switch, so the
previous VP's vsync can still latch the pending configuration.
Patches 3 through 5 contain only minor follow-up cleanup.
Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
---
Cristian Ciocaltea (5):
drm/rockchip: vop2: Fix wrong wait target in layer cfg done check
drm/rockchip: vop2: Wait for layer cfg done before switching LAYERSEL_REGDONE_SEL
drm/rockchip: vop2: Delay old_{layer|port}_sel updates in setup_layer_mixer()
drm/rockchip: vop2: Drop redundant zero-init in setup_layer_mixer()
drm/rockchip: vop2: Use vop2->old_layer_sel directly in wait_for_layer_cfg_done()
drivers/gpu/drm/rockchip/rockchip_vop2_reg.c | 46 +++++++++++++---------------
1 file changed, 22 insertions(+), 24 deletions(-)
---
base-commit: d4c14903bf5e28e740516c4fbb7db01e0dedf3af
change-id: 20260504-vop2-layer-cfg-tmout-73617a0a103c
On Mon, 04 May 2026 21:23:58 +0300, Cristian Ciocaltea wrote:
> On RK3588/RK3568 boards with multiple active display outputs, start/stop
> transitions may trigger a timeout during overlay layer configuration:
>
> rockchip-drm display-subsystem: [drm] *ERROR* wait layer cfg done timeout
>
> The shared OVL_LAYER_SEL and OVL_PORT_SEL shadow registers are committed
> to the active configuration at the vsync of whichever Video Port is
> selected by LAYERSEL_REGDONE_SEL. When two Video Ports race through
> atomic commits, rk3568_vop2_setup_layer_mixer() has two issues that
> cause the wait to poll for a value the hardware might not be able to
> produce.
>
> [...]
Applied, thanks!
[1/5] drm/rockchip: vop2: Fix wrong wait target in layer cfg done check
commit: 9f5670802df085ad343146561e69bac43e9905d2
[2/5] drm/rockchip: vop2: Wait for layer cfg done before switching LAYERSEL_REGDONE_SEL
commit: d1ad644e572c0647ad8428439eafea0aacfccf9e
[3/5] drm/rockchip: vop2: Delay old_{layer|port}_sel updates in setup_layer_mixer()
commit: 6a2f7339191b652f7ff998595df90987b33c3fda
[4/5] drm/rockchip: vop2: Drop redundant zero-init in setup_layer_mixer()
commit: bc5ffd6fc30cc52983d95fbe8783bb4233db6f86
[5/5] drm/rockchip: vop2: Use vop2->old_layer_sel directly in wait_for_layer_cfg_done()
commit: dc3de97433db03157ba6f87b6494ff1ad416a5a8
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
Hello Cristian,
On 5/5/26 02:23, Cristian Ciocaltea wrote:
> On RK3588/RK3568 boards with multiple active display outputs, start/stop
> transitions may trigger a timeout during overlay layer configuration:
>
> rockchip-drm display-subsystem: [drm] *ERROR* wait layer cfg done timeout
>
> The shared OVL_LAYER_SEL and OVL_PORT_SEL shadow registers are committed
> to the active configuration at the vsync of whichever Video Port is
> selected by LAYERSEL_REGDONE_SEL. When two Video Ports race through
> atomic commits, rk3568_vop2_setup_layer_mixer() has two issues that
> cause the wait to poll for a value the hardware might not be able to
> produce.
>
> Patch 1 fixes passing the wrong target to the wait function, since the
> expected value was already overwritten with the current VP's new
> layer_sel before reaching the wait.
>
> Patch 2 moves the wait before the LAYERSEL_REGDONE_SEL switch, so the
> previous VP's vsync can still latch the pending configuration.
>
> Patches 3 through 5 contain only minor follow-up cleanup.
>
> Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
Thank you very much for your work, these fixes all look sensible.
However, I haven't been able to construct a scenario via weston that
reproduce these issues. Could you please tell me how you triggered them?
> ---
> Cristian Ciocaltea (5):
> drm/rockchip: vop2: Fix wrong wait target in layer cfg done check
> drm/rockchip: vop2: Wait for layer cfg done before switching LAYERSEL_REGDONE_SEL
> drm/rockchip: vop2: Delay old_{layer|port}_sel updates in setup_layer_mixer()
> drm/rockchip: vop2: Drop redundant zero-init in setup_layer_mixer()
> drm/rockchip: vop2: Use vop2->old_layer_sel directly in wait_for_layer_cfg_done()
>
> drivers/gpu/drm/rockchip/rockchip_vop2_reg.c | 46 +++++++++++++---------------
> 1 file changed, 22 insertions(+), 24 deletions(-)
> ---
> base-commit: d4c14903bf5e28e740516c4fbb7db01e0dedf3af
> change-id: 20260504-vop2-layer-cfg-tmout-73617a0a103c
>
>
Hi Andy, On 6/1/26 1:54 PM, Andy Yan wrote: > Hello Cristian, > > On 5/5/26 02:23, Cristian Ciocaltea wrote: >> On RK3588/RK3568 boards with multiple active display outputs, start/stop >> transitions may trigger a timeout during overlay layer configuration: >> >> rockchip-drm display-subsystem: [drm] *ERROR* wait layer cfg done timeout >> >> The shared OVL_LAYER_SEL and OVL_PORT_SEL shadow registers are committed >> to the active configuration at the vsync of whichever Video Port is >> selected by LAYERSEL_REGDONE_SEL. When two Video Ports race through >> atomic commits, rk3568_vop2_setup_layer_mixer() has two issues that >> cause the wait to poll for a value the hardware might not be able to >> produce. >> >> Patch 1 fixes passing the wrong target to the wait function, since the >> expected value was already overwritten with the current VP's new >> layer_sel before reaching the wait. >> >> Patch 2 moves the wait before the LAYERSEL_REGDONE_SEL switch, so the >> previous VP's vsync can still latch the pending configuration. >> >> Patches 3 through 5 contain only minor follow-up cleanup. >> >> Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com> > > > Thank you very much for your work, these fixes all look sensible. Thanks for checking this out! > However, I haven't been able to construct a scenario via weston that > reproduce these issues. Could you please tell me how you triggered them? It was really tricky to reproduce - a customer usecase repeatedly restarting one of their apps under a customized Weston, and all that when having both HDMI output ports active, where at least one drives a 4K display. Regards, Cristian
© 2016 - 2026 Red Hat, Inc.