Comment # 27
on bug 106597
from Lukas Wunner
Okay the real culprit seems to be commit 3b5b899ca67d ("ALSA: hda: Make use of
core codec functions to sync power state"):
https://git.kernel.org/linus/3b5b899ca67d
If you revert that, does the issue go away?
I can see on my MacBook Pro that the return value is consistently 0x233 without
this commit when setting the power state to D3 (which is the correct return
value), and 0x1 with the commit. The commit went into 4.17. Given how late we
are in this cycle, I think a revert is in order. The commit breaks runtime
suspend for any HDA controller. Why the hell wasn't this discovered before,
this must have been in linux-next for > 4 months!?
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
