From: "Mark Dietzer" <git@doridian.net>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] drm: panel-backlight-quirks: Add Framework 16 panel
Date: Thu, 27 Feb 2025 18:40:12 -0800 [thread overview]
Message-ID: <1c96811e-4d54-480a-bc09-bcd2999e8e66@app.fastmail.com> (raw)
Similarly for the Framework 13 panels already handled in those quirks, the 16 can be helped by the same kind of patch.
I have run this on my own 16 for multiple months (hard coding the value to 0 before the quirks made it upstream) and it has resulted in a darker minimum brightness (as expected) and no issues.
The Framework community threads between the 13 and 16 for this improvement are the same one, so user reports in the link below will be mixed and likely more focused on the 13.
Link: https://community.frame.work/t/solved-even-lower-screen-brightness/25711/60
---
drivers/gpu/drm/drm_panel_backlight_quirks.c | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/drivers/gpu/drm/drm_panel_backlight_quirks.c b/drivers/gpu/drm/drm_panel_backlight_quirks.c
index c477d98ade2b..52aa2a7fa63e 100644
--- a/drivers/gpu/drm/drm_panel_backlight_quirks.c
+++ b/drivers/gpu/drm/drm_panel_backlight_quirks.c
@@ -41,6 +41,14 @@ static const struct drm_panel_min_backlight_quirk drm_panel_min_backlight_quirks
.ident.name = "NE135A1M-NY1",
.min_brightness = 0,
},
+ /* 16 inch panel */
+ {
+ .dmi_match.field = DMI_BOARD_VENDOR,
+ .dmi_match.value = "Framework",
+ .ident.panel_id = drm_edid_encode_panel_id('B', 'O', 'E', 0x0cb4),
+ .ident.name = "NE160QDM-NZ6",
+ .min_brightness = 0,
+ },
};
static bool drm_panel_min_backlight_quirk_matches(const struct drm_panel_min_backlight_quirk *quirk,
--
2.48.1
next reply other threads:[~2025-02-28 2:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 2:40 Mark Dietzer [this message]
2025-02-28 7:01 ` Thomas Weißschuh
2025-02-28 18:56 ` 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=1c96811e-4d54-480a-bc09-bcd2999e8e66@app.fastmail.com \
--to=git@doridian.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®