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 17:59:17 +0000 [thread overview]
Message-ID: <bug-203439-2300-RLYzcyWSUn@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203439-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203439
--- Comment #3 from Błażej Szczygieł (spaz16@wp.pl) ---
Thank you for the reply!
In bright room you can quickly disable the backlight (set it to 0) using the
Fn+F1 keys. You can save power and the display content doesn't disturb you, but
you can still notice that computer is working (the screen content can be still
visible). It is more convenient than DPMS, especially if you have duplicated
screen with HDMI and you don't want to reconfigure anything, just you want to
quickly disable the backlight.
Moreover, the current minimum backlight level is too bright for very dark room.
Sometimes I need to set to value of "2" or even "1" in kernel 4.20. Since
kernel 5.0 it is not possible and I'm not feeling convenient with too bright
display.
On Huawei Matebook D 14 the display doesn't flicker at all even on brightness
level 1 on kernel 4.20 (no PWM). Maybe it is a good idea to blacklist or
whitelist some devices? Or maybe it is a good idea to add an additional kernel
parameter to restore the old behavior and unlock all possible backlight levels
for more advanced users?
--
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 17:59 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
2019-04-26 17:59 ` bugzilla-daemon [this message]
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-RLYzcyWSUn@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).