Exactly the same situation as with the Framework 13. Value from ATIF is 12, which is quite bright as a minimum.
Additionally, disabling the custom curve produces a much more granular control, especially at lower brightness values. For now this can be done by the end-user by using `amdgpu.dcdebugmask=0x40000`. Signed-off-by: Samuel Dionne-Riel <[email protected]> --- Originally sent as: https://lore.kernel.org/dri-devel/[email protected]/ I have not resent the sibling patch sets, which implement further backlight quirks and handling to improve the experience with the device. I can resend them, but seeing that they are likely to incurr at least one round-trip of work, that seems a tad excessive. Sibling patch sets: - https://lore.kernel.org/dri-devel/[email protected]/ - https://lore.kernel.org/dri-devel/[email protected]/ Thank you all for your time! 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 537dc6dd05343..64a1c1f7abe76 100644 --- a/drivers/gpu/drm/drm_panel_backlight_quirks.c +++ b/drivers/gpu/drm/drm_panel_backlight_quirks.c @@ -60,6 +60,14 @@ static const struct drm_get_panel_backlight_quirk drm_panel_min_backlight_quirks .dmi_match_other.value = "Galileo", .quirk = { .min_brightness = 1, }, }, + /* Minisforum V3 SE */ + { + .dmi_match.field = DMI_BOARD_VENDOR, + .dmi_match.value = "Shenzhen Meigao Electronic Equipment Co.,Ltd", + .dmi_match_other.field = DMI_PRODUCT_NAME, + .dmi_match_other.value = "V3 SE", + .quirk = { .min_brightness = 1, }, + }, /* Have OLED Panels with brightness issue when last byte is 0/1 */ { .dmi_match.field = DMI_SYS_VENDOR, base-commit: 63804fed149a6750ffd28610c5c1c98cce6bd377 -- 2.51.0
