From: Louis Chauvet <louis.chauvet@bootlin.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
dri-devel@lists.freedesktop.org
Cc: harry.wentland@amd.com, Xaver Hugl <xaver.hugl@gmail.com>,
amd-gfx@lists.freedesktop.org,
Mario Limonciello <superm1@kernel.org>
Subject: Re: [PATCH v3 0/8] Add support for a DRM backlight capability
Date: Mon, 4 May 2026 15:55:52 +0200 [thread overview]
Message-ID: <0f5cf41c-99d5-4427-86fe-18c4f1e2c95e@bootlin.com> (raw)
In-Reply-To: <20260424220953.167058-1-mario.limonciello@amd.com>
On 4/25/26 00:09, Mario Limonciello wrote:
> From: Mario Limonciello (AMD) <superm1@kernel.org>
>
> At Display Next Hackfest 2025 we discussed the renewed need for moving
> brightness control into the DRM connector properties. I've taken the
> previous efforts from David and Marta, rebased and adjusted for the
> current kernel.
>
> The legacy sysfs interface is synchronized with the DRM connector (although
> the scale may be different as DRM connector property is u16).
>
> Later after this has been adopted by enough userspace, it may make sense to
> configure the legacy sysfs interface to be configurable so that only
> DRM master controls backlight.
>
> I've done a first implementation with amdgpu with eDP connectors; but
> conceivably this can be extended to other connectors like DP for displays
> that can be controlled via DDC as well later.
>
> I have also used DRM review prompts to review this series and fix some bugs
> which were caught with two different Claude models. The fixes are squashed
> into the patches.
>
> Assisted-by: Claude Opus
> Assisted-by: Claude Sonnet
>
> For ease of testing; this series is also available on this branch:
> https://git.kernel.org/pub/scm/linux/kernel/git/superm1/linux.git/log/?h=superm1/backlight-property-v3
Hello,
thanks for this work, I am very interested in this progress so I can
help you to test / implement more features.
I think you forgot to include the revert of "backlight: Remove notifier"
in your series, it can't be applied without it.
I will take a look and see if I can create a VKMS implementation of your
work.
Thanks for this work,
> David Rheinsberg (1):
> backlight: add kernel-internal backlight API
>
> Mario Limonciello (6):
> drm: link connectors to backlight devices
> DRM: Add support for client and driver indicating support for
> luminance
> drm/amd/display: Pass up errors reading actual brightness
> drm/amd: Indicate driver supports luminance
> drm/amd/display: Allow backlight registration to fail
> drm/amd/display: use drm backlight
>
> Marta Lofstedt (1):
> backlight: expose the current brightness in the new kernel API
>
> drivers/gpu/drm/Kconfig | 1 +
> drivers/gpu/drm/Makefile | 2 +
> drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 1 +
> .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 88 +++-
> drivers/gpu/drm/drm_atomic_uapi.c | 24 ++
> drivers/gpu/drm/drm_backlight.c | 406 ++++++++++++++++++
> drivers/gpu/drm/drm_connector.c | 12 +
> drivers/gpu/drm/drm_drv.c | 8 +
> drivers/gpu/drm/drm_ioctl.c | 10 +
> drivers/gpu/drm/drm_mode_config.c | 7 +
> drivers/gpu/drm/drm_mode_object.c | 66 ++-
> drivers/gpu/drm/drm_sysfs.c | 54 +++
> drivers/video/backlight/backlight.c | 83 ++++
> include/drm/drm_backlight.h | 45 ++
> include/drm/drm_connector.h | 8 +
> include/drm/drm_drv.h | 7 +
> include/drm/drm_file.h | 8 +
> include/drm/drm_mode_config.h | 5 +
> include/linux/backlight.h | 30 ++
> include/uapi/drm/drm.h | 10 +
> 20 files changed, 852 insertions(+), 23 deletions(-)
> create mode 100644 drivers/gpu/drm/drm_backlight.c
> create mode 100644 include/drm/drm_backlight.h
>
next prev parent reply other threads:[~2026-05-04 13:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 22:09 [PATCH v3 0/8] Add support for a DRM backlight capability Mario Limonciello
2026-04-24 22:09 ` [PATCH v3 1/8] backlight: add kernel-internal backlight API Mario Limonciello
2026-05-04 13:55 ` Louis Chauvet
2026-05-04 17:55 ` Mario Limonciello
2026-05-08 0:53 ` Louis Chauvet
2026-04-24 22:09 ` [PATCH v3 2/8] backlight: expose the current brightness in the new kernel API Mario Limonciello
2026-05-04 13:55 ` Louis Chauvet
2026-05-04 17:46 ` Mario Limonciello
2026-04-24 22:09 ` [PATCH v3 3/8] drm: link connectors to backlight devices Mario Limonciello
2026-04-25 12:41 ` Dmitry Baryshkov
2026-04-25 14:40 ` Mario Limonciello
2026-04-25 21:46 ` Dmitry Baryshkov
2026-04-24 22:09 ` [PATCH v3 4/8] DRM: Add support for client and driver indicating support for luminance Mario Limonciello
2026-04-25 12:17 ` Dmitry Baryshkov
2026-04-25 14:45 ` Mario Limonciello
2026-04-25 22:38 ` Dmitry Baryshkov
2026-05-08 0:53 ` Louis Chauvet
2026-04-24 22:09 ` [PATCH v3 5/8] drm/amd/display: Pass up errors reading actual brightness Mario Limonciello
2026-04-24 22:09 ` [PATCH v3 6/8] drm/amd: Indicate driver supports luminance Mario Limonciello
2026-04-24 22:09 ` [PATCH v3 7/8] drm/amd/display: Allow backlight registration to fail Mario Limonciello
2026-04-24 22:09 ` [PATCH v3 8/8] drm/amd/display: use drm backlight Mario Limonciello
2026-05-04 13:55 ` Louis Chauvet [this message]
2026-05-04 18:21 ` [PATCH v3 0/8] Add support for a DRM backlight capability Mario Limonciello
2026-05-11 23:11 ` Sebastian Wick
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=0f5cf41c-99d5-4427-86fe-18c4f1e2c95e@bootlin.com \
--to=louis.chauvet@bootlin.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=mario.limonciello@amd.com \
--cc=superm1@kernel.org \
--cc=xaver.hugl@gmail.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