public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: Add support for a DRM backlight capability
Date: Thu, 04 Jun 2026 14:54:30 +1000	[thread overview]
Message-ID: <review-overall-20260531114908.1693426-1-superm1@kernel.org> (raw)
In-Reply-To: <20260531114908.1693426-1-superm1@kernel.org>

Overall Series Review

Subject: Add support for a DRM backlight capability
Author: "Mario Limonciello (AMD)" <superm1@kernel.org>
Patches: 12
Reviewed: 2026-06-04T14:54:30.211806

---

This is v5 of a significant series by Mario Limonciello adding DRM connector-level backlight control via a new `LUMINANCE` property, replacing the legacy sysfs-only interface. The design is solid: connectors get an atomic property, a new `DRM_CLIENT_CAP_LUMINANCE` client capability inhibits legacy sysfs writes when a compositor takes over, and the backlight notifier is restored to allow cross-subsystem coordination.

The series has working compositor support in KWin, Mutter, and wlroots, which is a strong signal. The overall architecture of a `drm_backlight` intermediary that links DRM connectors to `backlight_device` instances is clean. Driver integration for amdgpu, i915/xe, and bridge connectors is provided.

However, there are several issues ranging from potential locking bugs to incomplete implementations and UAPI concerns that should be addressed before merge.

**Key concerns:**
1. **Spinlock + sleeping calls**: `drm_backlight_lock` is a spinlock, but several paths under it call functions that may sleep (kobject_uevent_env, backlight notifier calls).
2. **Per-device vs global property range**: The luminance property is global to the DRM device but the range is updated per-connector link, meaning multi-eDP setups will clobber each other's ranges.
3. **Incomplete inhibit implementation** in patch 3 (stubs), then filled in patch 4 — the intermediate state is confusing for bisection.
4. **Notification loop risk**: `backlight_update_status` now calls `backlight_notify_brightness` which notifies DRM, which may call back into backlight.
5. **drm_atomic_connector_commit_dpms signature change** — the upstream function takes `struct drm_atomic_commit *state`, but the patch diff shows `struct drm_atomic_state *state`, suggesting this may be based on an older tree.

---

---
Generated by Claude Code Patch Reviewer

      parent reply	other threads:[~2026-06-04  4:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-31 11:48 [PATCH v5 00/11] Add support for a DRM backlight capability Mario Limonciello (AMD)
2026-05-31 11:48 ` [PATCH v5 01/11] Revert "backlight: Remove notifier" Mario Limonciello (AMD)
2026-06-04  4:54   ` Claude review: " Claude Code Review Bot
2026-05-31 11:48 ` [PATCH v5 02/11] backlight: add kernel-internal backlight API Mario Limonciello (AMD)
2026-06-04  4:54   ` Claude review: " Claude Code Review Bot
2026-05-31 11:49 ` [PATCH v5 03/11] drm: link connectors to backlight devices Mario Limonciello (AMD)
2026-06-04  4:54   ` Claude review: " Claude Code Review Bot
2026-05-31 11:49 ` [PATCH v5 04/11] DRM: Add support for client indicating support for luminance Mario Limonciello (AMD)
2026-06-04  4:54   ` Claude review: " Claude Code Review Bot
2026-05-31 11:49 ` [PATCH v5 05/11] drm/amd/display: Pass up errors reading actual brightness Mario Limonciello (AMD)
2026-06-04  4:54   ` Claude review: " Claude Code Review Bot
2026-05-31 11:49 ` [PATCH v5 06/11] drm/amd/display: Allow backlight registration to fail Mario Limonciello (AMD)
2026-06-04  4:54   ` Claude review: " Claude Code Review Bot
2026-05-31 11:49 ` [PATCH v5 07/11] drm/amd/display: Move backlight tracing out of the dc lock Mario Limonciello (AMD)
2026-06-04  4:54   ` Claude review: " Claude Code Review Bot
2026-05-31 11:49 ` [PATCH v5 08/11] drm/amd/display: use drm backlight Mario Limonciello (AMD)
2026-06-04  4:54   ` Claude review: " Claude Code Review Bot
2026-05-31 11:49 ` [PATCH v5 09/11] drm/amd/display: Drop brightness caching in amdgpu_dm Mario Limonciello (AMD)
2026-06-04  4:54   ` Claude review: " Claude Code Review Bot
2026-05-31 11:49 ` [PATCH v5 10/11] drm/bridge: auto-link panel backlight in bridge connector Mario Limonciello (AMD)
2026-06-04  4:54   ` Claude review: " Claude Code Review Bot
2026-05-31 11:49 ` [PATCH v5 11/11] drm/i915/display: use drm backlight Mario Limonciello (AMD)
2026-06-04  4:54   ` Claude review: " Claude Code Review Bot
2026-06-04  4:54 ` Claude Code Review Bot [this message]

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=review-overall-20260531114908.1693426-1-superm1@kernel.org \
    --to=claude-review@example.com \
    --cc=dri-devel-reviews@example.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