From: Mario Limonciello <superm1@kernel.org>
To: Alex Hung <alex.hung@amd.com>
Cc: alexander.deucher@amd.com, christian.koenig@amd.com,
airlied@gmail.com, simona@ffwll.ch, harry.wentland@amd.com,
sunpeng.li@amd.com, siqueira@igalia.com, mwen@igalia.com,
tzimmermann@suse.de, ray.wu@amd.com, jpeisach@ubuntu.com,
cristian.ciocaltea@collabora.com, timur.kristof@gmail.com,
ivan.lipski@amd.com, chen-yu.chen@amd.com,
srinivasan.shanmugam@amd.com, amd-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/amd/display: Fix writeback completion timing
Date: Tue, 14 Jul 2026 22:24:58 -0500 [thread overview]
Message-ID: <a72d0fca-b938-4e6a-b994-6c84d315a6ed@kernel.org> (raw)
In-Reply-To: <20260711033159.3096477-1-alex.hung@amd.com>
On 7/10/26 22:31, Alex Hung wrote:
> [WHY]
> The out fence was signalled on the first vblank after arming, before the
> DMA finished copying, and the old code worked around this with an
> mdelay() in the IRQ handler.
>
> [HOW]
> Hold a vblank reference while writeback is pending and signal the out
> fence on the second vblank instead of using mdelay(). Add
> amdgpu_dm_crtc_complete_writeback() to finish and clean up writeback
> from both the IRQ and teardown paths.
>
> This can be verified by running IGT's kms_writeback 20 times without
> timeout errors.
>
> Assisted-by: Copilot:Claude-Opus-4.8
> Signed-off-by: Alex Hung <alex.hung@amd.com>
Reviewed-by: Mario Limonciello (AMD) <superm1@kernel.org>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_mode.h | 1 +
> .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 2 ++
> .../drm/amd/display/amdgpu_dm/amdgpu_dm_irq.c | 33 ++++++++++---------
> 3 files changed, 21 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_mode.h b/drivers/gpu/drm/amd/amdgpu/amdgpu_mode.h
> index 8069fc41cc7f..7c784277396a 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_mode.h
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_mode.h
> @@ -509,6 +509,7 @@ struct amdgpu_crtc {
> struct drm_pending_vblank_event *event;
>
> bool wb_pending;
> + bool wb_frame_done;
> bool wb_enabled;
> struct drm_writeback_connector *wb_conn;
> };
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> index d67dcaa3fa8f..0f5453649200 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
> @@ -4521,6 +4521,7 @@ bool amdgpu_dm_crtc_complete_writeback(struct amdgpu_crtc *acrtc)
> spin_lock_irqsave(&acrtc->wb_conn->job_lock, flags);
> pending = acrtc->wb_pending;
> acrtc->wb_pending = false;
> + acrtc->wb_frame_done = false;
> spin_unlock_irqrestore(&acrtc->wb_conn->job_lock, flags);
>
> if (!pending)
> @@ -4988,6 +4989,7 @@ static void dm_set_writeback(struct amdgpu_display_manager *dm,
> * cannot run its matching vblank_put before this get.
> */
> WARN_ON(drm_crtc_vblank_get(&acrtc->base));
> + acrtc->wb_frame_done = false;
> acrtc->wb_pending = true;
> }
>
> diff --git a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_irq.c b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_irq.c
> index c5467f34c51f..4de7fb264cb2 100644
> --- a/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_irq.c
> +++ b/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_irq.c
> @@ -1974,23 +1974,26 @@ static void dm_crtc_high_irq(void *interrupt_params)
> return;
>
> if (acrtc->wb_conn && acrtc->wb_pending) {
> - struct dc_stream_state *stream = acrtc->dm_irq_params.stream;
> - unsigned int v_total, refresh_hz;
> -
> - v_total = stream->adjust.v_total_max ?
> - stream->adjust.v_total_max : stream->timing.v_total;
> - refresh_hz = div_u64((uint64_t) stream->timing.pix_clk_100hz *
> - 100LL, (v_total * stream->timing.h_total));
> - mdelay(1000 / refresh_hz);
> -
> - /*
> - * Completion (signalling the out fence and releasing the vblank
> - * reference taken in dm_set_writeback()) is handled by the shared
> - * helper, which is also used by the teardown path.
> - */
> - if (amdgpu_dm_crtc_complete_writeback(acrtc))
> + if (acrtc->wb_frame_done) {
> + /*
> + * Second vblank: the DMA for the captured frame has
> + * had a full frame period to flush to memory. Signal
> + * the out fence now.
> + */
> + amdgpu_dm_crtc_complete_writeback(acrtc);
> + } else {
> + /*
> + * First vblank after arming: the frame has been
> + * scanned out and the DMA is finishing. Disable
> + * writeback immediately to prevent the hardware from
> + * starting a new capture that would overwrite the
> + * buffer. Signal completion on the next vblank to
> + * ensure the DMA is fully flushed to memory.
> + */
> dc_stream_fc_disable_writeback(adev->dm.dc,
> acrtc->dm_irq_params.stream, 0);
> + acrtc->wb_frame_done = true;
> + }
> }
>
> vrr_active = amdgpu_dm_crtc_vrr_active_irq(acrtc);
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-07-15 3:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-11 3:31 [PATCH] drm/amd/display: Fix writeback completion timing Alex Hung
2026-07-11 3:45 ` sashiko-bot
2026-07-15 3:24 ` Mario Limonciello [this message]
2026-07-17 21:00 ` Harry Wentland
2026-08-03 7:22 ` Christian König
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=a72d0fca-b938-4e6a-b994-6c84d315a6ed@kernel.org \
--to=superm1@kernel.org \
--cc=airlied@gmail.com \
--cc=alex.hung@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=chen-yu.chen@amd.com \
--cc=christian.koenig@amd.com \
--cc=cristian.ciocaltea@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=ivan.lipski@amd.com \
--cc=jpeisach@ubuntu.com \
--cc=mwen@igalia.com \
--cc=ray.wu@amd.com \
--cc=simona@ffwll.ch \
--cc=siqueira@igalia.com \
--cc=srinivasan.shanmugam@amd.com \
--cc=sunpeng.li@amd.com \
--cc=timur.kristof@gmail.com \
--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