<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <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#c20">Comment # 20</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 <a class="email" href="mailto:imre.deak@intel.com" title="Imre Deak <imre.deak@intel.com>"> Imre Deak</a> <pre>(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. > (And the unlimited block is anyway bad especially when the configuration is > dynamic; you can disable KMS easily via nomodeset, while the HD-audio driver > will still try to probe HDMI codec because it doesn't know that the graphics > side is disabled. Then it'll stall.) Can the above help?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>