<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [BAT SKL]igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c fails suspend autoresume"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94566#c34">Comment # 34</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [BAT SKL]igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c fails suspend autoresume"
href="https://bugs.freedesktop.org/show_bug.cgi?id=94566">bug 94566</a>
from <span class="vcard"><a class="email" href="mailto:imre.deak@intel.com" title="Imre Deak <imre.deak@intel.com>"> <span class="fn">Imre Deak</span></a>
</span></b>
<pre>(In reply to Takashi Iwai from <a href="show_bug.cgi?id=94566#c33">comment #33</a>)
<span class="quote">> Yes, a null bind or similar way to inform to component master was also what
> I had in my mind. This should help in case i915 KMS is disabled
> intentionally or fails initialization.</span >
Great, so I'll try to put together something that does this from the i915 side.
<span class="quote">> The rest cases are basically configuration errors (e.g. missing i915 module
> on media), and this could be covered by timeout. Then at least user will
> see the error instead of the forever silent.
>
> The next question is whether the i915 power is really mandatory before
> issuing the vendor id verb for HDMI codec on HDA bus. If this can be
> skipped, the things will be easier...</span ></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 the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>