From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106228] amdgpu reads back brightness 0 (which is not true) if checked before a brightness has been explicitly set
Date: Tue, 08 May 2018 21:06:02 +0000 [thread overview]
Message-ID: <bug-106228-502-JOQ9gNIiVt@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106228-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 471 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106228
--- Comment #2 from Harry Wentland <harry.wentland@amd.com> ---
That patch only affects Carrizo and should only be needed for S3.
We don't see this issue with Ubuntu 18.04 on a Raven laptop we have available.
The OS (Gnome) shows brightness as expected on boot.
I wonder if some laptops behave differently but I can't think why.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1371 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-05-08 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 3:43 [Bug 106228] amdgpu reads back brightness 0 (which is not true) if checked before a brightness has been explicitly set bugzilla-daemon
2018-05-08 19:45 ` bugzilla-daemon
2018-05-08 21:06 ` bugzilla-daemon [this message]
2018-06-05 15:38 ` bugzilla-daemon
2018-07-23 18:32 ` bugzilla-daemon
2018-07-24 20:06 ` bugzilla-daemon
2018-07-25 10:05 ` bugzilla-daemon
2018-07-25 10:07 ` bugzilla-daemon
2018-07-25 19:26 ` bugzilla-daemon
2018-07-26 7:41 ` 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-106228-502-JOQ9gNIiVt@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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).