From: Hugo Sales <hugo@hsal.es>
To: Mario Limonciello <superm1@kernel.org>,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, dri-devel@lists.freedesktop.org
Cc: airlied@gmail.com, simona@ffwll.ch, alexander.deucher@amd.com,
harry.wentland@amd.com, amd-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm: panel-backlight-quirks: Add ASUS ROG Flow X13 3840x2400 panel
Date: Tue, 3 Nov 2026 00:30:03 +0000 (WET) [thread overview]
Message-ID: <461302854.306462.1793665803972@app.mailbox.org> (raw)
In-Reply-To: <7b87b864-7896-4260-aad6-a78687201c0f@kernel.org>
On 11/2/26 23:13, Mario Limonciello wrote:
> Was this from looking at a datasheet or from empirical measurements?
> The reason it was safe to do on the Framework panel was because there
> was a confirmation the datasheet allowed a lower value.
>
> We don't want to be damaging hardware running it outside of spec.
Oh, damn, I didn't consider it could be damaging the panel and that it
could be out of spec. I did try looking for a datasheet for the
LQ134R1JW51 before sending this, but couldn't find one, and since it
"worked" (the panel stays lit at requested brightness 0, which reads
back as PWM 0 in amdgpu_current_backlight_pwm), I thought it was ok...
I've asked two people at ASUS whether the panel spec allows a lower
duty cycle, and I'll report back here. If you know someone who could
be of help, I'd appreciate the suggestion
One thing I noticed: 12 is also AMDGPU_DM_DEFAULT_MIN_BACKLIGHT, and
it's what this machine's ATIF returned, as did the Framework's, for
completely different panels. So the 12 ASUS returns for this Sharp
panel looks like the AMD reference value passed through, not a number
ASUS took from Sharp's datasheet. Do you or anyone else here know if
that could be the case?
Another data point is the VBT dumped from the BIOS of the ROG Flow Z13
2022 (GZ301ZE BIOS 321), which ships the LQ134R1JW52 (vs my
LQ134R1JW51). It sets brightness_min_level to 0 and the older
min_brightness field to 6, so i915 already lets that machine go down
to PWM 0. This doesn't really settle anything for the JW51, though
Assume the patch can be discarded unless I get a reply from ASUS, in
which case I'll reply here again
prev parent reply other threads:[~2026-11-03 0:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-31 13:45 Hugo Sales
2026-11-02 23:13 ` Mario Limonciello
2026-11-03 0:30 ` Hugo Sales [this message]
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=461302854.306462.1793665803972@app.mailbox.org \
--to=hugo@hsal.es \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--cc=superm1@kernel.org \
--cc=tzimmermann@suse.de \
/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
all inboxes | Powered by JetHome®