From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 203439] amdgpu: [REG 4.20 -> 5.0] Brightness minimum level is too high
Date: Fri, 26 Apr 2019 16:58:41 +0000 [thread overview]
Message-ID: <bug-203439-2300-bPdaqSW6QW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203439-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203439
Nicholas Kazlauskas (nicholas.kazlauskas@amd.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nicholas.kazlauskas@amd.com
--- Comment #2 from Nicholas Kazlauskas (nicholas.kazlauskas@amd.com) ---
At some point we started reading the ACPI backlight caps to respect the actual
backlight range for the panel. We map the backlight level specified by the user
from 0-255 to that range.
In the case where the caps aren't valid we use a default minimum brightness
that's non-zero since some panels will flash when the backlight level goes to
zero.
While I don't know offhand the reasoning for 12 specifically I also don't think
we'll be dropping it back down to zero.
Wouldn't DPMS off give you what you want in this case?
--
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:[~2019-04-26 16:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 16:39 [Bug 203439] New: amdgpu: [REG 4.20 -> 5.0] Brightness minimum level is too high bugzilla-daemon
2019-04-26 16:41 ` [Bug 203439] " bugzilla-daemon
2019-04-26 16:58 ` bugzilla-daemon [this message]
2019-04-26 17:59 ` bugzilla-daemon
2020-10-03 11:42 ` bugzilla-daemon
2020-10-03 11:45 ` bugzilla-daemon
2021-11-24 2:44 ` 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-203439-2300-bPdaqSW6QW@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).