From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 203905] amdgpu:actual_brightness has unreal/wrong value
Date: Sat, 01 Aug 2020 12:04:53 +0000 [thread overview]
Message-ID: <bug-203905-2300-gOShG1G6D0@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203905-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203905
Kunal Bhat (kunal.bhat2001@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kunal.bhat2001@gmail.com
--- Comment #9 from Kunal Bhat (kunal.bhat2001@gmail.com) ---
(In reply to Flo Bock from comment #8)
> With recent systemd changes, the 16 bit values in actual_brightness break
> saving and restoring the backlight values using AMDGPU. According to a
> closed issue on Github, Lennart Poettering sees this as a kernel issue[1].
> Is there any good reason for actual_brightness to be 16bit, whereas both
> max_brightness and brightness are 8bit?
>
> [1]: https://github.com/systemd/systemd/issues/16600
I believe it's there to provide a higher range of precision for the backlight.
Not sure why they never extended the range for max_brightness.
The systemd devs are adamant that this is a driver issue, and aren't ready to
implement a work around for it.
I believe this is the open issue with the discussions right now:
https://github.com/systemd/systemd/issues/16630
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-08-01 12:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-15 20:02 [Bug 203905] New: amdgpu:actual_brightness has unreal/wrong value bugzilla-daemon
2019-06-17 9:44 ` [Bug 203905] " bugzilla-daemon
2019-06-17 10:48 ` bugzilla-daemon
2019-09-26 21:07 ` bugzilla-daemon
2020-02-05 5:34 ` bugzilla-daemon
2020-02-05 5:52 ` bugzilla-daemon
2020-02-09 13:33 ` bugzilla-daemon
2020-02-10 19:16 ` bugzilla-daemon
2020-07-30 6:15 ` bugzilla-daemon
2020-08-01 12:04 ` bugzilla-daemon [this message]
2020-08-03 20:13 ` bugzilla-daemon
2020-08-04 20:15 ` bugzilla-daemon
2020-08-17 9:46 ` bugzilla-daemon
2020-08-31 10:46 ` bugzilla-daemon
2020-09-01 19:07 ` bugzilla-daemon
2020-09-08 0:59 ` bugzilla-daemon
2020-09-08 1:00 ` bugzilla-daemon
2020-09-08 1:03 ` bugzilla-daemon
2020-11-23 21:02 ` bugzilla-daemon
2020-12-07 10:17 ` bugzilla-daemon
2021-02-02 14:06 ` bugzilla-daemon
2021-02-07 22:17 ` bugzilla-daemon
2021-02-08 20:47 ` bugzilla-daemon
2021-02-17 17:24 ` bugzilla-daemon
2021-02-17 17:25 ` bugzilla-daemon
2021-03-15 10:58 ` bugzilla-daemon
2021-03-25 13:58 ` bugzilla-daemon
2021-03-25 14:03 ` bugzilla-daemon
2021-03-27 8:45 ` bugzilla-daemon
2021-05-06 10:12 ` bugzilla-daemon
2021-05-06 11:50 ` bugzilla-daemon
2021-05-06 11:56 ` bugzilla-daemon
2021-05-06 13:28 ` bugzilla-daemon
2021-05-06 14:20 ` 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-203905-2300-gOShG1G6D0@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).