From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 202445] amdgpu/dc: framerate dropping below adaptive sync range causes screen flickering
Date: Mon, 18 Mar 2019 17:44:34 +0000 [thread overview]
Message-ID: <bug-202445-2300-6mLl0oTz39@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202445-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=202445
--- Comment #28 from Clément Guérin (libcg@protonmail.com) ---
Nevermind. This commit was merged right before 5.0 was released. So yes, it was
in the tree.
What I suspect is happening is that a couple or more frames are scheduled by
the BTR code, but for some reason they are displayed at the max refresh rate
(144Hz in my case), then the monitor times out on the last frame and that
produces flickering. Which is what I pointed out in comment 16.
EDIT: I just realized that the link in that comment is outdated because code
moved around. This is what it originally pointed to:
https://github.com/torvalds/linux/blob/672e78c/drivers/gpu/drm/amd/display/modules/freesync/freesync.c#L980
/* TODO: pass in flag for Pre-DCE12 ASIC
* in order for frame variable duration to take affect,
* it needs to be done one VSYNC early, which is at
* frameCounter == 1.
* For DCE12 and newer updates to V_TOTAL_MIN/MAX
* will take affect on current frame
*/
As far as I know that will only affect pre-Vega GPUs, and I'm running Fiji.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-03-18 17:44 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 4:53 [Bug 202445] New: amdgpu/dc: framerate dropping below adaptive sync range causes screen flickering bugzilla-daemon
2019-01-29 14:48 ` [Bug 202445] " bugzilla-daemon
2019-01-29 15:46 ` bugzilla-daemon
2019-01-29 15:47 ` bugzilla-daemon
2019-01-30 14:02 ` bugzilla-daemon
2019-01-30 16:50 ` bugzilla-daemon
2019-01-30 16:53 ` bugzilla-daemon
2019-01-30 17:04 ` bugzilla-daemon
2019-01-31 5:36 ` bugzilla-daemon
2019-01-31 6:17 ` bugzilla-daemon
2019-02-02 22:39 ` bugzilla-daemon
2019-02-03 23:28 ` bugzilla-daemon
2019-02-03 23:51 ` bugzilla-daemon
2019-02-04 4:59 ` bugzilla-daemon
2019-02-04 15:44 ` bugzilla-daemon
2019-02-04 16:41 ` bugzilla-daemon
2019-02-07 8:00 ` bugzilla-daemon
2019-02-07 14:24 ` bugzilla-daemon
2019-02-25 19:13 ` bugzilla-daemon
2019-02-28 4:57 ` bugzilla-daemon
2019-03-01 16:43 ` bugzilla-daemon
2019-03-01 16:45 ` bugzilla-daemon
2019-03-01 16:54 ` bugzilla-daemon
2019-03-11 15:45 ` bugzilla-daemon
2019-03-15 15:57 ` bugzilla-daemon
2019-03-16 8:30 ` bugzilla-daemon
2019-03-18 13:07 ` bugzilla-daemon
2019-03-18 15:25 ` bugzilla-daemon
2019-03-18 17:44 ` bugzilla-daemon [this message]
2019-03-28 3:45 ` bugzilla-daemon
2019-04-28 0:57 ` bugzilla-daemon
2019-04-29 13:31 ` bugzilla-daemon
2019-06-03 10:56 ` bugzilla-daemon
2019-09-16 2:33 ` bugzilla-daemon
2019-09-16 13:22 ` bugzilla-daemon
2019-09-16 14:58 ` bugzilla-daemon
2019-09-16 15:02 ` bugzilla-daemon
2020-02-15 23:20 ` bugzilla-daemon
2020-04-07 15:07 ` bugzilla-daemon
2020-04-07 15:10 ` bugzilla-daemon
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=bug-202445-2300-6mLl0oTz39@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/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;
as well as URLs for NNTP newsgroup(s).