From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206575] [amdgpu] [drm] No video signal on resume from suspend, R9 380
Date: Wed, 15 Apr 2020 11:43:12 +0000 [thread overview]
Message-ID: <bug-206575-2300-q5WL1hGUDO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206575-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206575
--- Comment #26 from Noel Maersk (veox+kernel@veox.pw) ---
Will close as resolved shortly.
I did run a second bisect successfully, showing:
f2988e67144a263e33aa3b916457bf3095288c94 is the first new commit
commit f2988e67144a263e33aa3b916457bf3095288c94
Author: Yongqiang Sun <yongqiang.sun@amd.com>
Date: Fri Oct 18 18:24:59 2019 -0400
drm/amd/display: optimize bandwidth after commit streams.
[Why]
System is unable to enter S0i3 due to DISPLAY_OFF_MASK not asserted
in SMU.
[How]
Optimized bandwidth should be called paired and to resolve unplug
display underflow issue, optimize bandwidth after commit streams is
moved to next page flip, in case of S0i3, there is a change for no
flip coming causing display count is 1 in SMU side.
Add optimize bandwidth after commit stream.
Signed-off-by: Yongqiang Sun <yongqiang.sun@amd.com>
Reviewed-by: Tony Cheng <Tony.Cheng@amd.com>
Acked-by: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drivers/gpu/drm/amd/display/dc/core/dc.c | 4 ++++
1 file changed, 4 insertions(+)
--
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:[~2020-04-15 11:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 16:28 [Bug 206575] New: [amdgpu] [drm] No video signal on resume from suspend, R9 380 bugzilla-daemon
2020-02-17 16:29 ` [Bug 206575] " bugzilla-daemon
2020-02-17 16:29 ` bugzilla-daemon
2020-02-17 16:30 ` bugzilla-daemon
2020-02-17 16:30 ` bugzilla-daemon
2020-02-17 16:33 ` bugzilla-daemon
2020-02-17 16:38 ` bugzilla-daemon
2020-02-18 17:47 ` bugzilla-daemon
2020-02-18 21:33 ` bugzilla-daemon
2020-02-18 21:44 ` bugzilla-daemon
2020-02-18 22:06 ` bugzilla-daemon
2020-02-19 19:51 ` bugzilla-daemon
2020-02-21 0:42 ` bugzilla-daemon
2020-02-24 2:12 ` bugzilla-daemon
2020-03-16 9:39 ` bugzilla-daemon
2020-03-20 19:54 ` bugzilla-daemon
2020-03-20 20:15 ` bugzilla-daemon
2020-03-20 22:03 ` bugzilla-daemon
2020-03-23 5:06 ` bugzilla-daemon
2020-03-24 20:11 ` bugzilla-daemon
2020-04-10 8:35 ` bugzilla-daemon
2020-04-11 13:56 ` bugzilla-daemon
2020-04-11 13:59 ` bugzilla-daemon
2020-04-14 9:09 ` bugzilla-daemon
2020-04-14 13:28 ` bugzilla-daemon
2020-04-14 13:31 ` bugzilla-daemon
2020-04-14 14:10 ` bugzilla-daemon
2020-04-15 11:43 ` bugzilla-daemon [this message]
2020-04-15 11:44 ` bugzilla-daemon
2020-04-15 11:45 ` 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-206575-2300-q5WL1hGUDO@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).