diff options
author | Hans de Goede <hdegoede@redhat.com> | 2022-05-16 11:32:33 +0200 |
---|---|---|
committer | Hans de Goede <hdegoede@redhat.com> | 2022-09-03 12:17:26 +0200 |
commit | c0f50c5de93b8afb2281009a33c124e82973e457 (patch) | |
tree | b3746315e19f25c50399de24416fd7f71352dd4e /certs | |
parent | c053383813fd17296db99cea78e058ed4d53019c (diff) | |
download | linux-c0f50c5de93b8afb2281009a33c124e82973e457.tar.bz2 |
drm/amdgpu: Register ACPI video backlight when skipping amdgpu backlight registration
Typically the acpi_video driver will initialize before amdgpu, which
used to cause /sys/class/backlight/acpi_video0 to get registered and then
amdgpu would register its own amdgpu_bl# device later. After which
the drivers/acpi/video_detect.c code unregistered the acpi_video0 device
to avoid there being 2 backlight devices.
This means that userspace used to briefly see 2 devices and the
disappearing of acpi_video0 after a brief time confuses the systemd
backlight level save/restore code, see e.g.:
https://bbs.archlinux.org/viewtopic.php?id=269920
To fix this the ACPI video code has been modified to make backlight class
device registration a separate step, relying on the drm/kms driver to
ask for the acpi_video backlight registration after it is done setting up
its native backlight device.
Add a call to the new acpi_video_register_backlight() when amdgpu skips
registering its own backlight device because of either the firmware_flags
or the acpi_video_get_backlight_type() return value. This ensures that
if the acpi_video backlight device should be used, it will be available
before the amdgpu drm_device gets registered with userspace.
Acked-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Diffstat (limited to 'certs')
0 files changed, 0 insertions, 0 deletions