From: Lauri Tirkkonen <lauri@hacktheplanet.fi>
To: Mario Limonciello <superm1@kernel.org>
Cc: stable@vger.kernel.org, regressions@lists.linux.dev,
amd-gfx@lists.freedesktop.org,
Mario Limonciello <mario.limonciello@amd.com>,
Wayne Lin <wayne.lin@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [REGRESSION] drm/amd/display: backlight brightness set to 0 at amdgpu initialization
Date: Fri, 18 Jul 2025 23:36:17 +0900 [thread overview]
Message-ID: <aHpb4ZTZ5FoOBUrZ@hacktheplanet.fi> (raw)
In-Reply-To: <d92458bf-fc2b-47bf-b664-9609a3978646@kernel.org>
On Fri, Jul 18 2025 08:10:06 -0500, Mario Limonciello wrote:
> Do you by chance have an OLED panel? I believe what's going on is that
> userspace is writing zero or near zero and on OLED panels with older kernels
> this means non-visible.
Yes, this is an OLED panel. But I don't believe it's userspace writing
anything at this point in the boot; before the bisected commit,
brightness was set to 32 (out of max 255) on this hardware when I
checked from the initramfs rescue shell. At the bisected commit, it's 0
(out of max 255).
> There is another commit that fixes the behavior that is probably missing.
Which commit is that? It's not in 6.15.7?
--
Lauri Tirkkonen | lotheac @ IRCnet
next prev parent reply other threads:[~2025-07-20 15:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-18 7:29 [REGRESSION] drm/amd/display: backlight brightness set to 0 at amdgpu initialization Lauri Tirkkonen
2025-07-18 13:10 ` Mario Limonciello
2025-07-18 14:36 ` Lauri Tirkkonen [this message]
2025-07-18 17:13 ` Mario Limonciello
2025-07-19 1:03 ` Lauri Tirkkonen
2025-07-19 1:14 ` Mario Limonciello
2025-07-19 2:12 ` Lauri Tirkkonen
2025-07-19 15:25 ` Mario Limonciello
2025-07-19 17:39 ` Mario Limonciello
2025-07-20 9:34 ` Lauri Tirkkonen
2025-07-20 9:36 ` [REGRESSION] [PATCH] drm/amd/display: fix initial backlight brightness calculation Lauri Tirkkonen
2025-07-20 10:26 ` Greg Kroah-Hartman
2025-07-21 0:51 ` Lauri Tirkkonen
2025-07-20 12:49 ` Mario Limonciello
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=aHpb4ZTZ5FoOBUrZ@hacktheplanet.fi \
--to=lauri@hacktheplanet.fi \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=mario.limonciello@amd.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=superm1@kernel.org \
--cc=wayne.lin@amd.com \
/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.