search for: use_vga_switcheroo

...s located on the GPU, so the GPU needs to be on for the HDA controller to do anything useful. This commit implicitly fixes an unbalanced runtime PM ref upon unbind of hda_intel.c: On ->probe, a runtime PM ref was previously released under the condition "azx_has_pm_runtime(chip) || hda->use_vga_switcheroo", but on ->remove a runtime PM ref was only acquired under the first of those conditions. Thus, binding and unbinding the driver twice on a vga_switcheroo capable system caused the runtime PM refcount to drop below zero. The issue is resolved because the AZX_DCAPS_PM_RUNTIME flag is now a...

...; so the GPU needs to be on for the HDA controller to do anything useful. > > This commit implicitly fixes an unbalanced runtime PM ref upon unbind of > hda_intel.c: On ->probe, a runtime PM ref was previously released under > the condition "azx_has_pm_runtime(chip) || hda->use_vga_switcheroo", but > on ->remove a runtime PM ref was only acquired under the first of those > conditions. Thus, binding and unbinding the driver twice on a > vga_switcheroo capable system caused the runtime PM refcount to drop > below zero. The issue is resolved because the AZX_DCAPS_PM_R...

Modernize vga_switcheroo by using a "device link" to enforce a runtime PM dependency from an HDA controller to the GPU it's integrated into. Remove thereby obsoleted code and fix a bunch of bugs. Device links were introduced in v4.10. Users might see a small power saving if the discrete GPU is in use and its HDA controller is not, because the HDA controller is now allowed to runtime

Modernize vga_switcheroo by using a device link to enforce a runtime PM dependency from an HDA controller to the GPU it's integrated into, v2. Changes since v1: - Replace patch [1/7] to use pci_save_state() / pci_restore_state() for consistency between runtime PM code path of bound and unbound devices. (Rafael, Bjorn) - Patch [5/7]: Drop an unnecessary initialization. (Bjorn) Rephrase