From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 220326] New: Mismatch between the meanings of brightness and actual_brightness
Date: Tue, 08 Jul 2025 16:35:06 +0000 [thread overview]
Message-ID: <bug-220326-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=220326
Bug ID: 220326
Summary: Mismatch between the meanings of brightness and
actual_brightness
Product: Drivers
Version: 2.5
Hardware: AMD
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: kernvirt@gmail.com
Regression: No
Amd ryzen 5 7520u (Mendocino)
/sys/class/backlight/amdgpu_bl1/type = raw
max_brightness = 255
Bug: The meaning of brightness does not match the meaning of actual_brightness
in /sys/class/backlight/amdgpu_bl1. For example, I set brightness 160 and
actual_brightness at this moment = 100, Also for example 80/25. In other words,
the higher the brightness level I set, the larger the adjustment step per
brightness percentage becomes of actual_brightness, for example 0-4% brightness
in kde = 0 in actual_brightness, While the difference between 40 and 45% is
already 11 units in actual_brightness.
Tested kernels:6.13-6.15.5
Distro - debian/fedora/arch
I've tried:
-kernel parameters: acpi_backlight=video/vendor/native
amdgpu.backlight=0
-brightnessctl, acpilight
-tty, DE
Everywhere the result is the same as I described above.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2025-07-08 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 16:35 bugzilla-daemon [this message]
2025-07-10 13:05 ` [Bug 220326] Mismatch between the meanings of brightness and actual_brightness bugzilla-daemon
2025-07-11 5:20 ` bugzilla-daemon
2025-07-11 6:04 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-220326-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.