From: Maxime Ripard <mripard@kernel.org>
To: Harry Wentland <harry.wentland@amd.com>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
dri-devel@lists.freedesktop.org, Simona Vetter <simona@ffwll.ch>,
Alex Deucher <alexander.deucher@amd.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
Xaver Hugl <xaver.hugl@gmail.com>,
amd-gfx@lists.freedesktop.org,
"open list:INTEL DRM DISPLAY FOR XE AND I915 DRIVERS"
<intel-gfx@lists.freedesktop.org>,
"open list:INTEL DRM DISPLAY FOR XE AND I915 DRIVERS"
<intel-xe@lists.freedesktop.org>,
Hans de Goede <hansg@kernel.org>,
David Herrmann <dh.herrmann@gmail.com>,
Mario Limonciello <superm1@kernel.org>
Subject: Re: [PATCH v8 04/14] drm: add connector backlight (LUMINANCE) infrastructure
Date: Fri, 2 Oct 2026 10:00:03 +0200 [thread overview]
Message-ID: <ar9kR_SmugvIVIuR@houat> (raw)
In-Reply-To: <25c3dd77-bedc-4822-b687-0ea429db0dc7@amd.com>
[-- Attachment #1: Type: text/plain, Size: 1849 bytes --]
On Thu, Oct 01, 2026 at 03:12:25PM -0400, Harry Wentland wrote:
> On 2026-09-08 00:40, Mario Limonciello wrote:
> > Backlight brightness is a property of a display, and thus of a DRM
> > connector, yet it has historically only been controllable through the
> > separate backlight sysfs interface. Add a generic, backend-agnostic
> > per-connector LUMINANCE range property so brightness can be driven
> > through the atomic modeset path like any other connector state.
> >
> > A struct drm_backlight is embedded in every connector and initialized by
> > the core; drivers do not allocate it. A driver links a backend (today a
> > backlight_device, in the future DDC/CI, MIPI-DCS, ...) with
> > drm_backlight_link(), which creates the connector's LUMINANCE property
>
> I didn't follow the whole discussion so I'm curious why we decided to
> name this LUMINANCE. I think of nits or cd/m^2 when I hear luminance.
> I think it's dangerous when we use for a property that is currently
> not able to describe the output in nits. You would also then have to
> define whether you're dealing with a fully white screen, or parts that
> are white. In short, you're ending up in color management territory where
> these things have specific meanings and it's easy to get it wrong if
> we don't define the nuances right.
>
> Why not simply call it BACKLIGHT, which is what it is? Later, if we then
> add support for luminance (in absolute nits) we can use the LUMINANCE
> term for that. Otherwise it'll be lost to us and be apt to confuse
> people.
>
> I'm on the fence about calling it "drm brightness", as suggested by Jani,
> but could get onboard with something like PANEL_BRIGHTNESS.
I don't think we should mention panel here, it will be useful for at
least HDMI and DP too.
brightness works for me though
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
next prev parent reply other threads:[~2026-10-02 8:00 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 4:40 [PATCH v8 00/14] Add support for a DRM backlight capability Mario Limonciello
2026-09-08 4:40 ` [PATCH v8 01/14] Revert "backlight: Remove notifier" Mario Limonciello
2026-09-08 4:51 ` sashiko-bot
2026-09-08 4:40 ` [PATCH v8 02/14] backlight: add kernel-internal backlight API Mario Limonciello
2026-09-08 4:52 ` sashiko-bot
2026-09-08 15:45 ` Jani Nikula
2026-09-08 16:00 ` Mario Limonciello
2026-09-08 16:33 ` Jani Nikula
2026-09-22 8:23 ` Thomas Zimmermann
2026-09-22 8:49 ` Javier Martinez Canillas
2026-09-22 11:34 ` Mario Limonciello
2026-09-22 12:05 ` Thomas Zimmermann
2026-09-25 12:52 ` Xaver Hugl
2026-09-22 12:26 ` Maxime Ripard
2026-09-22 11:37 ` Mario Limonciello
2026-09-08 4:40 ` [PATCH v8 03/14] drm/property: add a per-connector luminance flag Mario Limonciello
2026-09-08 4:54 ` sashiko-bot
2026-09-22 8:32 ` Thomas Zimmermann
2026-09-25 16:30 ` Leo Li
2026-10-01 19:05 ` Harry Wentland
2026-09-08 4:40 ` [PATCH v8 04/14] drm: add connector backlight (LUMINANCE) infrastructure Mario Limonciello
2026-09-08 4:54 ` sashiko-bot
2026-09-08 15:48 ` Jani Nikula
2026-09-22 11:42 ` Javier Martinez Canillas
2026-09-22 12:08 ` Thomas Zimmermann
2026-09-22 11:58 ` Thomas Zimmermann
2026-10-01 19:12 ` Harry Wentland
2026-10-01 19:29 ` Xaver Hugl
2026-10-02 8:00 ` Maxime Ripard [this message]
2026-09-08 4:40 ` [PATCH v8 05/14] drm: add DRM_CLIENT_CAP_LUMINANCE Mario Limonciello
2026-09-08 4:55 ` sashiko-bot
2026-09-08 4:40 ` [PATCH v8 06/14] drm/amd/display: Pass up errors reading actual brightness Mario Limonciello
2026-09-08 4:40 ` [PATCH v8 07/14] drm/amd: Indicate driver supports luminance Mario Limonciello
2026-09-22 8:53 ` Thomas Zimmermann
2026-09-08 4:40 ` [PATCH v8 08/14] drm/amd/display: use drm backlight Mario Limonciello
2026-09-08 4:57 ` sashiko-bot
2026-09-08 4:40 ` [PATCH v8 09/14] drm/amdgpu: Check bios_scratch_reg_offset in backlight level helper Mario Limonciello
2026-09-08 4:51 ` sashiko-bot
2026-09-08 4:40 ` [PATCH v8 10/14] drm/amd/display: Update KUnit backlight tests for luminance property and fixtures Mario Limonciello
2026-09-08 4:54 ` sashiko-bot
2026-09-08 4:40 ` [PATCH v8 11/14] drm/bridge: auto-link panel backlight in bridge connector Mario Limonciello
2026-09-08 4:40 ` [PATCH v8 12/14] drm/xe: Indicate support for luminance on the connector Mario Limonciello
2026-09-08 4:57 ` sashiko-bot
2026-09-08 4:40 ` [PATCH v8 13/14] drm/i915: " Mario Limonciello
2026-09-08 4:40 ` [PATCH v8 14/14] drm/i915/display: use drm backlight Mario Limonciello
2026-09-08 5:03 ` sashiko-bot
2026-09-08 9:32 ` ✓ i915.CI.BAT: success for Add support for a DRM backlight capability (rev3) Patchwork
2026-09-08 18:45 ` ✗ i915.CI.Full: failure " Patchwork
2026-09-22 8:33 ` [PATCH v8 00/14] Add support for a DRM backlight capability Javier Martinez Canillas
2026-09-22 11:41 ` Mario Limonciello
2026-09-22 12:16 ` Maxime Ripard
2026-09-22 12:23 ` Thomas Zimmermann
2026-09-22 12:35 ` Maxime Ripard
2026-09-23 6:39 ` Thomas Zimmermann
2026-10-01 16:06 ` Maxime Ripard
2026-10-01 16:10 ` Mario Limonciello
2026-10-01 16:20 ` Maxime Ripard
2026-09-23 8:07 ` Xaver Hugl
2026-10-01 16:18 ` Maxime Ripard
2026-10-01 16:21 ` Mario Limonciello
2026-10-01 16:55 ` Javier Martinez Canillas
2026-10-02 8:01 ` Maxime Ripard
2026-09-22 12:28 ` Javier Martinez Canillas
2026-09-23 20:12 ` 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=ar9kR_SmugvIVIuR@houat \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dh.herrmann@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hansg@kernel.org \
--cc=harry.wentland@amd.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mario.limonciello@amd.com \
--cc=simona@ffwll.ch \
--cc=superm1@kernel.org \
--cc=tzimmermann@suse.de \
--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