<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [SKL/KBL] Init time is high"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94722#c15">Comment # 15</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [SKL/KBL] Init time is high"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94722">bug 94722</a>
from <span class="vcard"><a class="email" href="mailto:david.weinehall@intel.com" title="David Weinehall <david.weinehall@intel.com>"> <span class="fn">David Weinehall</span></a>
</span></b>
<pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=94722#c12">comment #12</a>)
<span class="quote">> There are a couple of other things to consider. The init/resume time being
> measured here is how long we are blocking the boot/resume from starting
> userspace. It is quite acceptable for userspace to start before the panel is
> lit, for example.
>
> From boot, the target is set assuming that the BIOS has already prelit all
> the outputs, in which case we are measuring and trying to minimise the
> latency of the driver taking over the existing hw state.</span >
That only applies to the init-target, however, not the suspend/resume targets
also listed here; I don't think we can rely on just taking over the existing hw
state from BIOS for S0/S0ix/S3. Agreed?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>