From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: Harry Wentland <harry.wentland@amd.com>,
Leo Li <sunpeng.li@amd.com>,
Rodrigo Siqueira <siqueira@igalia.com>,
Alex Deucher <alexander.deucher@amd.com>
Cc: "Christian König" <christian.koenig@amd.com>,
"Fangzhi Zuo" <Jerry.Zuo@amd.com>,
"Aurabindo Pillai" <aurabindo.pillai@amd.com>,
"George Zhang" <george.zhang@amd.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [REGRESSION 7.3] drm/amd/display: single-frame scanout corruption on DCN32 at 120 Hz since a637a140ab86
Date: Mon, 19 Oct 2026 03:39:05 +0500 [thread overview]
Message-ID: <20261018223905.32324-1-mikhail.v.gavrilov@gmail.com> (raw)
In-Reply-To: <20261011201833.853907-1-mikhail.v.gavrilov@gmail.com>
The workaround from my previous mail does not survive a suspend. After
resume from S3 the band was back (seen, not measured) with the TV still
in FreeSync mode, because DC had turned SubVP back on.
Snapshots of amdgpu_dm_capabilities, pp_dpm_mclk and the DTN log, all
at 3840x2160@120 with FreeSync enabled (vrr_range 40-120, the EDID
byte-identical in every snapshot):
after boot sub-viewport disabled, UCLK at 1249 MHz
20 s after rtcwake -m mem sub-viewport enabled, UCLK switching,
watermark set A at the register maximum
after toggling Night Light sub-viewport disabled again
dcn32_allow_subvp_high_refresh_rate() keeps SubVP off a single FreeSync
display by reading stream->allow_freesync, but amdgpu_dm sets that
field only on the first flip after a commit, so the modeset forced on
resume is validated without it. A gamma change makes DC validate the
state again, this time with the field set. The patch:
https://lore.kernel.org/all/20261018221726.27259-1-mikhail.v.gavrilov@gmail.com/
With it, SubVP stays disabled across rtcwake -m mem. Until it is
merged, toggling Night Light after resume restores the workaround.
None of this changes the band itself: in HDMI VRR mode, and at 100 Hz
in either mode, DC uses SubVP anyway.
--
Thanks,
Mikhail
next prev parent reply other threads:[~2026-10-18 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-29 1:05 Mikhail Gavrilov
2026-09-02 7:32 ` Mikhail Gavrilov
2026-09-19 20:08 ` Mikhail Gavrilov
2026-10-11 20:18 ` Mikhail Gavrilov
2026-10-18 22:39 ` Mikhail Gavrilov [this message]
2026-10-27 22:32 ` Mikhail Gavrilov
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=20261018223905.32324-1-mikhail.v.gavrilov@gmail.com \
--to=mikhail.v.gavrilov@gmail.com \
--cc=Jerry.Zuo@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=aurabindo.pillai@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=george.zhang@amd.com \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=siqueira@igalia.com \
--cc=sunpeng.li@amd.com \
/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
all inboxes | Powered by JetHome®