Skip to content

Commit 8ecd32b

Browse files
committed
docs: backlight: Clarify actual_brightness
Currently userspace software systemd treats `brightness` and `actual_brightness` identically due to a bug found in an out of tree driver. This however causes problems for in-tree drivers that use brightness to report user requested `brightness` and `actual_brightness` to report what the hardware actually has programmed. Clarify the documentation to match the behavior described in commit 6ca0176 ("[PATCH] backlight: Backlight Class Improvements"). Cc: Lee Jones <[email protected]> Cc: Lennart Poettering <[email protected]> Cc: [email protected] Link: systemd/systemd#36881 Reviewed-by: Harry Wentland <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Mario Limonciello <[email protected]>
1 parent 5093504 commit 8ecd32b

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

Documentation/ABI/stable/sysfs-class-backlight

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,12 @@ Date: March 2006
2626
KernelVersion: 2.6.17
2727
Contact: Richard Purdie <[email protected]>
2828
Description:
29-
Show the actual brightness by querying the hardware.
29+
Show the actual brightness by querying the hardware. Due
30+
to implementation differences in hardware this may not
31+
match the value in 'brightness'. For example some hardware
32+
may treat blanking differently or have custom power saving
33+
features. Userspace should generally use the values in
34+
'brightness' to make decisions.
3035
Users: HAL
3136

3237
What: /sys/class/backlight/<backlight>/max_brightness

0 commit comments

Comments
 (0)