From: Maxime Ripard <mripard@kernel.org>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: dri-devel@lists.freedesktop.org, harry.wentland@amd.com,
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>
Subject: Re: [PATCH v9 07/21] drm: add panel and bridge connector luminance forwarding
Date: Mon, 12 Oct 2026 10:41:10 +0200 [thread overview]
Message-ID: <asyc2ufs5fdpEYrp@houat> (raw)
In-Reply-To: <20261002190030.211356-8-mario.limonciello@amd.com>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
On Fri, Oct 02, 2026 at 02:00:16PM -0500, Mario Limonciello wrote:
> Forward connector luminance operations through panel and bridge connectors.
> Allow bridges that own brightness control to expose luminance operations,
> and route panel bridges to the panel backlight backend.
>
> Attach the property only when a usable brightness backend is present and
> CONFIG_DRM_LUMINANCE is enabled.
>
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
This should be split into multiple patches: one to enable luminance
support for bridges, one to do so for panels, and then hook everything
into drm_bridge_connector.
Also, we still have some direct panel consumers, so I don't think we
can handle it at the bridge level yet.
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 273 bytes --]
next prev parent reply other threads:[~2026-10-12 8:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-02 19:00 [PATCH v9 00/21] Add support for a DRM backlight capability Mario Limonciello
2026-10-02 19:00 ` [PATCH v9 01/21] drm: add connector LUMINANCE property Mario Limonciello
2026-10-03 11:37 ` Javier Martinez Canillas
2026-10-02 19:00 ` [PATCH v9 02/21] drm/amd/display: Pass up errors reading actual brightness Mario Limonciello
2026-10-02 19:00 ` [PATCH v9 03/21] drm/amd: add luminance property support Mario Limonciello
2026-10-02 19:00 ` [PATCH v9 04/21] drm/amdgpu: Check bios_scratch_reg_offset in backlight level helper Mario Limonciello
2026-10-02 19:00 ` [PATCH v9 05/21] drm/amd/display: update KUnit luminance fixtures Mario Limonciello
2026-10-02 19:00 ` [PATCH v9 06/21] drm/i915/display: add luminance property support Mario Limonciello
2026-10-02 19:00 ` [PATCH v9 07/21] drm: add panel and bridge connector luminance forwarding Mario Limonciello
2026-10-12 8:41 ` Maxime Ripard [this message]
2026-10-02 19:00 ` [PATCH v9 08/21] drm/mipi-dbi: add connector luminance helpers Mario Limonciello
2026-10-03 11:03 ` Javier Martinez Canillas
2026-10-02 19:00 ` [PATCH v9 09/21] drm/tiny: migrate panel-mipi-dbi to connector luminance Mario Limonciello
2026-10-03 11:22 ` Javier Martinez Canillas
2026-10-02 19:00 ` [PATCH v9 10/21] drm/tiny: migrate HX8357D " Mario Limonciello
2026-10-02 19:00 ` [PATCH v9 11/21] drm/tiny: migrate ILI9163 " Mario Limonciello
2026-10-02 19:00 ` [PATCH v9 12/21] drm/tiny: migrate ILI9341 " Mario Limonciello
2026-10-02 19:00 ` [PATCH v9 13/21] drm/tiny: migrate ILI9486 " Mario Limonciello
2026-10-02 19:00 ` [PATCH v9 14/21] drm/tiny: migrate MI0283QT " Mario Limonciello
2026-10-02 19:00 ` [PATCH v9 15/21] drm/sitronix: migrate ST7735R " Mario Limonciello
2026-10-02 19:00 ` [PATCH v9 16/21] drm/nouveau: add connector luminance support Mario Limonciello
2026-10-02 19:00 ` [PATCH v9 17/21] drm/gud: " Mario Limonciello
2026-10-02 19:00 ` [PATCH v9 18/21] drm/radeon: " Mario Limonciello
2026-10-02 19:00 ` [PATCH v9 19/21] drm/gma500: " Mario Limonciello
2026-10-02 19:00 ` [PATCH v9 20/21] drm/bridge: add PS8622 " Mario Limonciello
2026-10-02 19:00 ` [PATCH v9 21/21] drm/solomon: add SSD130x " Mario Limonciello
2026-10-03 10:30 ` Javier Martinez Canillas
2026-10-03 10:39 ` Javier Martinez Canillas
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=asyc2ufs5fdpEYrp@houat \
--to=mripard@kernel.org \
--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=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=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