[Bug 94439] [BXT-P/APL] DP and HDMI will stop output after resumed from S3

[bugzilla-daemon at freedesktop.org]

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

--- Comment #31 from Humberto Israel Perez Rodriguez <humberto.i.perez.rodriguez at intel.com> ---
(In reply to Imre Deak from comment #30)
> (In reply to Humberto Israel Perez Rodriguez from comment #28)
> > (In reply to Imre Deak from comment #27)
> > > I believe that S3 failing in itself (so not the hotplug issue originally
> > > reported) is not a BIOS issue. I could reproduce it on my machine with a
> > > recent BIOS:
> > > APLKRVPA.X64.0130.B11.1603210634
> > > 
> > > With a few fixes S3 works now for me and those fixes could be also relevant
> > > here.
> > > So Humberto, besides trying to upgrade the BIOS as Yann suggested could you
> > > also try the following branch:
> > > https://github.com/ideak/linux/commits/bxt-rpm
> > 
> > Hi Imre Deak :
> > 
> > i tried with a newer bios 131.10 and the branch :
> > https://github.com/ideak/linux/commits/bxt-rpm, but is the same issue, after
> > return from S3 the HDMI is not seen and xrandr also does not recognize it
> > 
> > kernel info
> > ==================
> > commit 068ab4d97212c00defebf525821001785c7caf2e
> > Author: Imre Deak <imre.deak at intel.com>
> > Date:   Fri Apr 8 20:40:16 2016 +0300
> > 
> >     drm/i915/bxt: Sanitize DC state tracking after suspend-to-ram and -disk
> > 
> >     After suspend-to-ram or -disk we don't know what power state the display
> >     is, DC0 or DC9 are both possible states, so reset the DC software
> > tracking
> >     in these cases. This gets rid of 'DC state mismatch' error messages
> >     during suspend to ram and disk which is a false positive based on the
> >     above.
> > 
> >     Signed-off-by: Imre Deak <imre.deak at intel.com>
> > 
> > branch = bxt-rmp
> > kernel = 4.6.0-rc2
> 
> Well, in comment#23 you said:
> "the DUT is not able to resume from S3 if is connected any external display
> (DP / HDMI)"
> 
> This means to me that not only that HDMI is not detected after S3 resume,
> but S3 doesn't work at all, that is the machine hangs or similar generic
> issue. Could you clarify what did you mean in comment#23? That is does S3
> work at all for you with current -nightly (is the system still alive, can
> you SSH in)? With the above branch do you have working eDP/DP after S3
> suspend/resume?
> 
> Not detecting HDMI after S3 is expected. The HDMI port is routed through the
> LSPCON protocol converter and the driver doesn't have support for that
> (patches are under review). Since BIOS configures LSPCON you will have a
> working output right after booting, but that configuration will be lost
> after S3 suspend/resume.

In the comment 23, i said that only with the commit
d252bf68b75792108ae2821c3a6e1cdc58e88cb9 i was not able to resume by second
time , but with any other commit from drm-intel-nightly s3 works without issue.

with the branch https://github.com/ideak/linux/commits/bxt-rpm, i can resume
from S3 with eDP, i did not try with DP because right now our other BXT-P is
busy, in my current BXT only has eDP + HDMI (DP port is not working)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160408/34243237/attachment.html>