diff options
author | Hans de Goede <hdegoede@redhat.com> | 2023-02-15 12:38:33 +0100 |
---|---|---|
committer | Alex Deucher <alexander.deucher@amd.com> | 2023-02-23 17:35:59 -0500 |
commit | d24b77e444bef83155557ebf4c2b3c551f198926 (patch) | |
tree | c678e46c0f934ffe37a1a4ddd6f54a0a3dbfa431 /drivers/crypto/sa2ul.h | |
parent | 424b3d7582a2a4a7c45d405225ac70cff97f2e4a (diff) |
drm/amd/display: Pass proper parent for DM backlight device registration
The parent for the backlight device should be the drm-connector object,
not the PCI device.
Userspace relies on this to be able to detect which backlight class device
to use on hybrid gfx devices where there may be multiple native (raw)
backlight devices registered.
Specifically gnome-settings-daemon expects the parent device to have
an "enabled" sysfs attribute (as drm_connector devices do) and tests
that this returns "enabled" when read.
This aligns the parent of the backlight device with i915, nouveau, radeon.
Note that drivers/gpu/drm/amd/amdgpu/atombios_encoders.c also already
uses the drm_connector as parent, only amdgpu_dm.c used the PCI device
as parent before this change.
Note this is marked as a RFC because I don't have hw to test, so this
has only been compile tested! If someone can test this on actual
hw which hits the changed code path that would be great.
Link: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/730
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'drivers/crypto/sa2ul.h')
0 files changed, 0 insertions, 0 deletions