<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#c24">Comment # 24</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#c22">comment #22</a>)
<span class="quote">> (In reply to Imre Deak from <a href="show_bug.cgi?id=94566#c20">comment #20</a>)
> > (In reply to Takashi Iwai from <a href="show_bug.cgi?id=94566#c17">comment #17</a>)
> > > And, one more problem is that we gather up the all codecs as a single card.
> > > Blocking a probe of one codec means to block the probe of the whole card.
> > > So we can't take unlimited block behavior.
> >
> > Can you still separate interface registration from HW access? I assume the
> > latter could be delay until the user first opens the device node, so you
> > could do the blocking there and register the corresponding interface earlier.
>
> It's difficult, unfortunately. HDMI codec may provide multiple streams (or
> even zero stream), and for knowing how many streams, we need to probe. So,
> without probing, we don't know which device interface to provide.
>
> And, on SKL architecture, the HDMI codec is on the same HDA bus that is
> represented as a single sound card instance. </span >
Why can't the HDMI codec be on a separate sound card?
<span class="quote">> A delayed probe means the dynamic addition / removal of PCM and other
> devices. However, most of user-space stuff like PA doesn't work in that way
> (although it's possible in kernel API level). They support only the
> card-level hotplug.</span ></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<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>