dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 108575] amd-staging-drm-next, R4 Mullins hdmi monitor wont wake up from S3 - *ERROR* REG_WAIT timeout 1us * 80000 tries - dce_abm_immediate_disable
Date: Sat, 16 Feb 2019 09:31:07 +0000	[thread overview]
Message-ID: <bug-108575-502-9Lk8JkeztY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-108575-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 639 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=108575

--- Comment #4 from Przemek <soprwa@gmail.com> ---
Yesterday I have observed a strange behavior.

After suspend/resume cycle HDMI screen is turned off, but when you trigger
hibernate/resume after suspend/resume HDMI output is turned back on and is
working properly.
(Yes, hibernation works on CIK and amdgpu now!! Thank you so much!!)

As given above a question arise,
are there other-different triggers/resets in suspend/resume and
hibernate/resume cycles for those asics?

Thanks,
Przemek.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1594 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-02-16  9:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-27 10:29 [Bug 108575] amd-staging-drm-next, R4 Mullins hdmi monitor wont wake up from S3 - *ERROR* REG_WAIT timeout 1us * 80000 tries - dce_abm_immediate_disable bugzilla-daemon
2018-11-25  8:11 ` bugzilla-daemon
2018-12-16 20:45 ` bugzilla-daemon
2018-12-16 20:59 ` bugzilla-daemon
2019-02-16  9:31 ` bugzilla-daemon [this message]
2019-02-23 14:06 ` 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-108575-502-9Lk8JkeztY@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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