<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#c7">Comment # 7</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:david.weinehall@intel.com" title="David Weinehall <david.weinehall@intel.com>"> David Weinehall</a> <pre>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? 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". The ~16ms schedule_timeout() is where we wait for vblank before programming vblanks; that section is covered by a FIXME and a TODO, so that bit is a known issue. The remaining slow-poke is intel_opregion_setup() (63ms). I must admit that I cannot explain that slowdown without diving further into the code; our kabylake here does not exhibit this behaviour; I just ran a test on a machine in our lab--that function took roughly 6ms.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>