Over on Bug 104064 Alex Deucher and Harry =
Wentland had heroically assisted me
in finally fixing dGPU auto-suspend on my HG laptop (Intel iGPU + AMD dGPU)=
. I
was really looking forward to their work going mainline in 4.16 and me being
able to enjoy my newly working system. Unfortunately, some other commit into
4.16 broke things again. After overcoming my initial frustration and doing =
some
research, I was now able to track this down to the work by Lukas Wunner on
vga_switcheroo.
I am doing my debugging with drm-next-4.18-wip over at
https://cgit.freedesk=
top.org/~agd5f/linux because 4.16 & 4.17 have one other
bug that 4.18 doesn't (Bug 105760) that prevent me from u=
sing those. Simply
compiling drm-next-4.18-wip will result in a kernel that cannot dynamically
power down the dGPU. It remains up regardless of use status and draws power.
Now if I revert commits 07f4f97d7b4bf325d9f558c5b58230387e4e57e0,
b67ae78efae0d5be5d9c7a507e67cd02971b32e1 and
2b4f44eec2be2688511c2b617d0e1b4f94c45ba4 and recompile, then the resulting
kernel will once again fully power down my dGPU when it is not in use.=20
Now, if I can assist in any way with further debugging or testing patches to
figure out what specifically went wrong with those patches, I'd be happy to=
do
so, just let me know!