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: driver core: count references of the platform device's fwnode, not OF node
Date: Mon, 25 May 2026 20:33:06 +1000	[thread overview]
Message-ID: <review-overall-20260521-pdev-fwnode-ref-v1-0-88c324a1b8d2@oss.qualcomm.com> (raw)
In-Reply-To: <20260521-pdev-fwnode-ref-v1-0-88c324a1b8d2@oss.qualcomm.com>

Overall Series Review

Subject: driver core: count references of the platform device's fwnode, not OF node
Author: Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>
Patches: 26
Reviewed: 2026-05-25T20:33:06.580208

---

This is a well-structured 23-patch series from Bartosz Golaszewski that addresses a real architectural gap in platform device firmware node refcounting. The series follows a sound methodology:

1. **Patches 1-5**: Fix existing refcount bugs where `of_node_get()` was missing
2. **Patches 6-8**: Introduce three new helper functions (`platform_device_set_of_node()`, `platform_device_set_fwnode()`, `platform_device_set_of_node_from_dev()`)
3. **Patches 9-22**: Convert all in-tree callers to use the new helpers
4. **Patch 23**: Switch from OF-only refcounting to generic fwnode refcounting

The overall design is correct. The key insight is that `platform_device_release()` currently only calls `of_node_put()`, so non-OF fwnode handles (software nodes, ACPI nodes) were never refcounted through the platform device lifecycle. By funneling all assignments through helpers first, patch 23 can atomically switch to `fwnode_handle_get()`/`fwnode_handle_put()` without breaking any caller.

The series is a prerequisite for unifying the release path for dynamic platform devices with unmanaged software nodes, which is a worthwhile goal.

**One concern**: The series depends on a function `dev_assign_of_node_reused()` (used in patch 23's `platform_device_register_full()` change) that does not exist in the current drm-next tree. This is presumably introduced in a companion series or different base. This should be clarified.

**DRM-specific impact**: Only patch 18 touches DRM code (`drivers/gpu/drm/xe/xe_i2c.c`), and it's a trivial mechanical conversion. Low risk for the DRM subsystem.

---
Generated by Claude Code Patch Reviewer

      parent reply	other threads:[~2026-05-25 10:33 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-21  8:36 [PATCH 00/23] driver core: count references of the platform device's fwnode, not OF node Bartosz Golaszewski
2026-05-21  8:36 ` [PATCH 01/23] mfd: tps6586x: fix OF node refcount Bartosz Golaszewski
2026-05-25 10:33   ` Claude review: " Claude Code Review Bot
2026-05-21  8:36 ` [PATCH 02/23] net: mv643xx: " Bartosz Golaszewski
2026-05-25 10:33   ` Claude review: " Claude Code Review Bot
2026-05-21  8:36 ` [PATCH 03/23] slimbus: qcom-ngd-ctrl: " Bartosz Golaszewski
2026-05-25 10:33   ` Claude review: " Claude Code Review Bot
2026-05-21  8:36 ` [PATCH 04/23] pmdomain: imx: " Bartosz Golaszewski
2026-05-25 10:33   ` Claude review: " Claude Code Review Bot
2026-05-21  8:36 ` [PATCH 05/23] powerpc/powermac: " Bartosz Golaszewski
2026-05-25 10:33   ` Claude review: " Claude Code Review Bot
2026-05-21  8:36 ` [PATCH 06/23] driver core: platform: provide platform_device_set_of_node() Bartosz Golaszewski
2026-05-25 10:33   ` Claude review: " Claude Code Review Bot
2026-05-21  8:36 ` [PATCH 07/23] driver core: platform: provide platform_device_set_fwnode() Bartosz Golaszewski
2026-05-25 10:33   ` Claude review: " Claude Code Review Bot
2026-05-21  8:36 ` [PATCH 08/23] driver core: platform: provide platform_device_set_of_node_from_dev() Bartosz Golaszewski
2026-05-25 10:33   ` Claude review: " Claude Code Review Bot
2026-05-21  8:36 ` [PATCH 09/23] of: platform: use platform_device_set_of_node() Bartosz Golaszewski
2026-05-21  8:36 ` [PATCH 10/23] powerpc/powermac: " Bartosz Golaszewski
2026-05-21  8:36 ` [PATCH 11/23] i2c: pxa-pci: " Bartosz Golaszewski
2026-05-21  9:13   ` Wolfram Sang
2026-05-21  8:36 ` [PATCH 12/23] iommu/fsl: " Bartosz Golaszewski
2026-05-21  9:44   ` Robin Murphy
2026-05-21  8:36 ` [PATCH 13/23] net: bcmgenet: " Bartosz Golaszewski
2026-05-21  8:36 ` [PATCH 14/23] pmdomain: imx: " Bartosz Golaszewski
2026-05-21  8:36 ` [PATCH 15/23] mfd: tps6586: " Bartosz Golaszewski
2026-05-21  8:36 ` [PATCH 16/23] slimbus: qcom-ngd-ctrl: " Bartosz Golaszewski
2026-05-21  8:36 ` [PATCH 17/23] net: mv643xx: " Bartosz Golaszewski
2026-05-21  8:36 ` [PATCH 18/23] drm/xe/i2c: use platform_device_set_fwnode() Bartosz Golaszewski
2026-05-21  8:36 ` [PATCH 19/23] platform/surface: gpe: " Bartosz Golaszewski
2026-05-21  8:36 ` [PATCH 20/23] usb: chipidea: use platform_device_set_of_node_from_dev() Bartosz Golaszewski
2026-05-21  8:36 ` [PATCH 21/23] usb: musb: " Bartosz Golaszewski
2026-05-21  8:36 ` [PATCH 22/23] reset: rzg2l: " Bartosz Golaszewski
2026-05-21  8:36 ` [PATCH 23/23] driver core: platform: count references to all kinds of firmware nodes Bartosz Golaszewski
2026-05-25 10:33   ` Claude review: " Claude Code Review Bot
2026-05-25 10:33 ` 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-20260521-pdev-fwnode-ref-v1-0-88c324a1b8d2@oss.qualcomm.com \
    --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