diff options
| author | Hans de Goede <hdegoede@redhat.com> | 2023-02-17 17:42:08 +0300 |
|---|---|---|
| committer | Hans de Goede <hdegoede@redhat.com> | 2023-02-18 13:45:52 +0300 |
| commit | 0d9bdd8a550170306c2021b8d6766c5343b870c2 (patch) | |
| tree | 890c2263158d6839926f113968ac743c2b963362 /crypto/dh.c | |
| parent | 3004e8d2a0a98bbf4223ae146464fadbff68bf78 (diff) | |
| download | linux-0d9bdd8a550170306c2021b8d6766c5343b870c2.tar.xz | |
platform/x86: nvidia-wmi-ec-backlight: Add force module parameter
On some Lenovo Legion models, the backlight might be driven by either
one of nvidia_wmi_ec_backlight or amdgpu_bl0 at different times.
When the Nvidia WMI EC backlight interface reports the backlight is
controlled by the EC, the current backlight handling only registers
nvidia_wmi_ec_backlight (and registers no other backlight interfaces).
This hides (never registers) the amdgpu_bl0 interface, where as prior
to 6.1.4 users would have both nvidia_wmi_ec_backlight and amdgpu_bl0
and could work around things in userspace.
Add a force module parameter which can be used with acpi_backlight=native
to restore the old behavior as a workound (for now) by passing:
"acpi_backlight=native nvidia-wmi-ec-backlight.force=1"
Fixes: 8d0ca287fd8c ("platform/x86: nvidia-wmi-ec-backlight: Use acpi_video_get_backlight_type()")
Link: https://bugzilla.kernel.org/show_bug.cgi?id=217026
Cc: stable@vger.kernel.org
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Reviewed-by: Daniel Dadap <ddadap@nvidia.com>
Link: https://lore.kernel.org/r/20230217144208.5721-1-hdegoede@redhat.com
Diffstat (limited to 'crypto/dh.c')
0 files changed, 0 insertions, 0 deletions