From: Philip Mueller <philm@manjaro.org>
To: Antheas Kapenekakis <lkml@antheas.dev>, amd-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Harry Wentland" <harry.wentland@amd.com>,
"Rodrigo Siqueira" <siqueira@igalia.com>,
"Mario Limonciello" <mario.limonciello@amd.com>,
"Peyton Lee" <peytolee@amd.com>, "Lang Yu" <lang.yu@amd.com>
Subject: Re: [PATCH v1 2/2] drm/amd/display: Adjust AUX brightness to be a granularity of 100
Date: Mon, 25 Aug 2025 09:02:34 +0200 [thread overview]
Message-ID: <88fec8864f2544df67113bf7282a1b2965a1eabd.camel@manjaro.org> (raw)
In-Reply-To: <CAGwozwH7m5CgGiK5Xu_q0JbJvRQbcHkgQd9nFXJNq3DQhWO7QQ@mail.gmail.com>
On Sun, 2025-08-24 at 21:33 +0200, Antheas Kapenekakis wrote:
> Well Phil managed to fall into the value 332800, which has a 0 minor
> bit. Unfortunate. In hindsight, every 256 hundreds there would be a
> zero anyway.
>
> Before I made this patch I made a partial refactor of panel-quirks
> where a quirk like this could go to. But I would really prefer not to
> do quirks. Ill send that too.
>
> Antheas
I was already looking into that OLED issue for several weeks. Changing
granularity might hid the root cause and you might hit the issue less
frequently.
Currently checking [1] which changes the first byte to 3 since when
DP_SOURCE_BACKLIGHT_LEVEL is written to with
the first byte being 0x00 and sometimes 0x01, the panel forcibly
turns off until the device sleeps again.
In the end the panel vendor has to fix it in firmware. If not a quirk
might be better specific for each panel vendor.
I'm still not sure if that refactoring is needed, or a separate quirk
function is more logical to be accepted upstream.
[1]
https://lore.kernel.org/lkml/20250824200202.1744335-5-lkml@antheas.dev/T/#u
next prev parent reply other threads:[~2025-08-26 7:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-24 8:53 [PATCH v1 1/2] drm/amdgpu/vpe: increase VPE_IDLE_TIMEOUT to fix hang on Strix Halo Antheas Kapenekakis
2025-08-24 8:53 ` [PATCH v1 2/2] drm/amd/display: Adjust AUX brightness to be a granularity of 100 Antheas Kapenekakis
2025-08-24 11:29 ` kernel test robot
2025-08-24 19:33 ` Antheas Kapenekakis
2025-08-25 7:02 ` Philip Mueller [this message]
2025-08-24 20:16 ` [PATCH v1 1/2] drm/amdgpu/vpe: increase VPE_IDLE_TIMEOUT to fix hang on Strix Halo Mario Limonciello
2025-08-24 20:46 ` Antheas Kapenekakis
2025-08-25 1:38 ` Mario Limonciello
2025-08-25 13:39 ` Antheas Kapenekakis
2025-08-26 13:41 ` Alex Deucher
2025-08-26 19:19 ` Mario Limonciello
2025-08-26 19:21 ` Antheas Kapenekakis
2025-08-26 20:12 ` Matthew Schwartz
2025-08-26 20:58 ` Antheas Kapenekakis
2025-08-27 0:50 ` Matthew Schwartz
2025-08-27 2:37 ` Lee, Peyton
2025-08-27 15:42 ` Matthew Schwartz
2025-08-25 13:20 ` Alex Deucher
2025-08-25 13:33 ` Antheas Kapenekakis
2025-08-25 14:01 ` Antheas Kapenekakis
2025-08-25 16:41 ` Mario Limonciello
2025-08-25 21:00 ` Antheas Kapenekakis
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=88fec8864f2544df67113bf7282a1b2965a1eabd.camel@manjaro.org \
--to=philm@manjaro.org \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=lang.yu@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@antheas.dev \
--cc=mario.limonciello@amd.com \
--cc=peytolee@amd.com \
--cc=simona@ffwll.ch \
--cc=siqueira@igalia.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 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).