summaryrefslogtreecommitdiff
path: root/drivers/pwm/pwm-hibvt.c
diff options
context:
space:
mode:
authorHans de Goede <hdegoede@redhat.com>2018-10-14 17:12:01 +0200
committerThierry Reding <thierry.reding@gmail.com>2018-10-16 13:15:57 +0200
commit4743765babb278a7d399df5733fc8a6b6bbedf3e (patch)
treecbd5ae9381fd5b93e5e017a2ae417a206873e359 /drivers/pwm/pwm-hibvt.c
parent6f37709fb0a61f09ca96348044c5bb13e333e518 (diff)
downloadlwn-4743765babb278a7d399df5733fc8a6b6bbedf3e.tar.gz
lwn-4743765babb278a7d399df5733fc8a6b6bbedf3e.zip
pwm: lpss: Force runtime-resume on suspend on Cherry Trail
On Cherry Trail devices under Windows the PWM controller used for the backlight is considered part of the GPU even though it is part of the LPSS block and thus is an entirely different independent hardware unit. Because of this on Cherry Trail the GPU's (GFX0 ACPI node) _PS3 and _PS0 methods save and restore the PWM controller registers. If userspace blanks the screen before suspending, such as e.g. GNOME does, then the PWM controller will be runtime-suspended when the suspend starts. This causes the GFX0 _PS? methods to save a value of 0xffffffff for the PWM control register and to restore this value on resume. 0xffffffff is not a valid value for the register and writing this causes problems such as e.g. a flickering backlight. This commit adds a prepare method to the dev_pm_ops and makes it return 0 on Cherry Trail devices forcing a runtime-resume before other device's suspend methods run. This fixes the reading and writing back of 0xffffffff. Since we now always runtime-resume the device on suspend, it will be resumed on resume too and we no longer need to check for the GFX0 _PS0 method having resumed it underneath us, so this commit removes the now no longer necessary complete dev_pm_op. Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Thierry Reding <thierry.reding@gmail.com>
Diffstat (limited to 'drivers/pwm/pwm-hibvt.c')
0 files changed, 0 insertions, 0 deletions