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: drm: tyr: use lifetime-bound IoMem
Date: Wed, 27 May 2026 15:26:02 +1000	[thread overview]
Message-ID: <review-overall-20260525230152.277820-1-dakr@kernel.org> (raw)
In-Reply-To: <20260525230152.277820-1-dakr@kernel.org>

Overall Series Review

Subject: drm: tyr: use lifetime-bound IoMem
Author: Danilo Krummrich <dakr@kernel.org>
Patches: 7
Reviewed: 2026-05-27T15:26:02.455706

---

This is a clean 2-patch refactoring series from Danilo Krummrich that modernizes the tyr (Arm Mali Valhall) DRM driver to use the new driver-core lifetime infrastructure. The series depends on a prerequisite patch set [1] that adds lifetime-bound driver data to the platform driver framework, and is based on drm-rust-next (not the drm-next tree available here — hence the apply failure and the substantial differences in the register access pattern).

**Patch 1** separates the `platform::Driver` trait implementation onto a new zero-sized `TyrPlatformDriver` type, keeping `TyrPlatformDriverData` as the associated `Data<'bound>` type. This is a standard pattern enabling the new GAT-based lifetime-bound driver data.

**Patch 2** takes advantage of that lifetime binding to use `IoMem<'a>` directly on the stack in probe, removing the `Devres`/`Arc` wrapping that was previously needed to satisfy `'static` requirements. This simplifies register access by eliminating the `(*iomem).access(dev)?` indirection.

The overall direction is good — the I/O memory is only used during probe and never stored in driver data, so the `Devres` revocation machinery was unnecessary overhead. One minor issue noted below.

---
Generated by Claude Code Patch Reviewer

      parent reply	other threads:[~2026-05-27  5:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-25 23:01 [PATCH 0/2] drm: tyr: use lifetime-bound IoMem Danilo Krummrich
2026-05-25 23:01 ` [PATCH 1/2] gpu: drm: tyr: separate driver type from driver data Danilo Krummrich
2026-05-26  1:17   ` Eliot Courtney
2026-05-26  6:43   ` Boris Brezillon
2026-05-27  5:26   ` Claude review: " Claude Code Review Bot
2026-05-25 23:01 ` [PATCH 2/2] gpu: drm: tyr: use IoMem directly instead of Devres Danilo Krummrich
2026-05-26  1:30   ` Alexandre Courbot
2026-05-26  2:43   ` Eliot Courtney
2026-05-27  5:26   ` Claude review: " Claude Code Review Bot
2026-05-27  5:26 ` 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-20260525230152.277820-1-dakr@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