<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [NVC1] HDMI audio device only visible after rescan" href="https://bugs.freedesktop.org/show_bug.cgi?id=75985#c118">Comment # 118</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [NVC1] HDMI audio device only visible after rescan" href="https://bugs.freedesktop.org/show_bug.cgi?id=75985">bug 75985</a> from <a class="email" href="mailto:prymoo@gmail.com" title="Przemysław Kopa <prymoo@gmail.com>"> Przemysław Kopa</a> <pre>(In reply to Lukas Wunner from <a href="show_bug.cgi?id=75985#c116">comment #116</a>) > @Przemysław Kopa: > > The fix was applied by Takashi Iwai on Thursday Oct 17 with commit > 94989e318b2f, it was merged to Linus' tree on Friday Oct 18 and will thus be > part of v5.4-rc4 due out later today. It should appear in v5.3-stable within > 1 or 2 weeks. You may want to double-check that the issue is gone with this > fix. Thanks, I can happily confirm that the issue is fixed in v5.4-rc4. :) > There's one problem remaining, you shouldn't have to manually echo "auto" to > the HDA's control file because we call pm_runtime_allow() on the HDA device > in drivers/pci/quirks.c:quirk_gpu_hda() -> pci_create_device_link(). > Something must be calling pm_runtime_forbid() afterwards, perhaps this is > triggered from user space on Arch Linux. I'm attaching a little debug patch > which logs a stacktrace to dmesg whenever pm_runtime_allow() / _forbid() is > called for a device. Feel free to attach dmesg output with this patch > applied and I'll be happy to take a look at it. I'm attaching dmesg dump - last stack trace is generated after me echoing "auto" to HDA control file.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>