<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Suspend and resume take long time on Dell XPS 13 9360 (Kaby Lake)" href="https://bugs.freedesktop.org/show_bug.cgi?id=99650#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Suspend and resume take long time on Dell XPS 13 9360 (Kaby Lake)" href="https://bugs.freedesktop.org/show_bug.cgi?id=99650">bug 99650</a> from <a class="email" href="mailto:pmenzel@molgen.mpg.de" title="Paul Menzel <pmenzel@molgen.mpg.de>"> Paul Menzel</a> <pre>(In reply to David Weinehall from <a href="show_bug.cgi?id=99650#c7">comment #7</a>) > Something seems to be really wrong with that graph you posted (suspend only > taking 0.011ms)--or did you filter these figures to only contain resume time? Indeed. Something seems off. I didn’t do anything besides running the script. It looks like there is a bug. > Anyhow, let's start with the low-hanging fruit: > > The 206ms spent in skl_update_crtcs() is the VBT-mandated panel on-timeout > (200ms) + DP link training. There's also cdclk programming which takes a few > milliseconds. This covers intel_display_resume(), which is the biggest > "culprit". Indeed. What are the options to improve that? My first naive and ignorant thought would be, on a laptop, and even desktop systems, the display doesn’t change during suspend/resume. So can this be cached, and those values tried first? […]</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>