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: platform: provide platform_device_set_of_node_from_dev()
Date: Mon, 25 May 2026 20:33:08 +1000	[thread overview]
Message-ID: <review-patch8-20260521-pdev-fwnode-ref-v1-8-88c324a1b8d2@oss.qualcomm.com> (raw)
In-Reply-To: <20260521-pdev-fwnode-ref-v1-8-88c324a1b8d2@oss.qualcomm.com>

Patch Review

```c
void platform_device_set_of_node_from_dev(struct platform_device *pdev,
					  const struct device *dev2)
{
	device_set_of_node_from_dev(&pdev->dev, dev2);
	pdev->dev.fwnode = of_fwnode_handle(pdev->dev.of_node);
}
```

This wraps `device_set_of_node_from_dev()` (which does `of_node_get`/`of_node_put` and sets `of_node_reused = true`) and then syncs the fwnode pointer.

**Minor concern for post-patch-23**: After patch 23 changes release to `fwnode_handle_put()`, this function sets `pdev->dev.fwnode` without calling `fwnode_handle_put()` on the old value first. If the old fwnode was a non-OF fwnode that was set via `platform_device_set_fwnode()` (which after patch 23 takes a ref via `fwnode_handle_get()`), this would leak. In practice this is extremely unlikely since these are called once on freshly allocated pdevs, but for symmetry with how `platform_device_set_fwnode()` works post-patch-23, consider implementing this as:
```c
platform_device_set_of_node(pdev, dev2->of_node);
pdev->dev.of_node_reused = true;
```
This would route through the helper chain and handle put/get correctly.

### PATCHES 9-22: Driver conversions

These are all mechanical conversions from direct `pdev->dev.of_node = ...` or `pdev->dev.fwnode = ...` assignments to using the new helpers. Each one is straightforward:

- **Patch 9** (of/platform): Replaces `device_set_node(&dev->dev, of_fwnode_handle(of_node_get(np)))` with `platform_device_set_of_node(dev, np)`. Clean simplification.

- **Patch 10** (powerpc/powermac): Converts the fix from patch 5 to use the helper. Removes the explicit `of_node_get()` since the helper does it internally.

- **Patch 11** (i2c/pxa-pci): Straightforward conversion.

- **Patch 12** (iommu/fsl): This one is interesting — in addition to the conversion, it restructures the error handling:
```c
-	pdev->dev.of_node = of_node_get(np);
+	platform_device_set_of_node(pdev, np);
 ...
+	of_node_put(np);
 	return 0;
 
 error_device_add:
-	of_node_put(pdev->dev.of_node);
-	pdev->dev.of_node = NULL;
-
 	platform_device_put(pdev);
```
The error path simplification is correct: `platform_device_put()` → `platform_device_release()` → `of_node_put()` handles the pdev's reference. The new `of_node_put(np)` on the success path drops the original search reference. The old error path code (`of_node_put` + NULL assignment) was being done manually because the caller wanted to avoid the double-put in `platform_device_release()`, but with the helper taking its own ref, `platform_device_put()` cleanly handles it. **However**, this patch is doing a subtle bug fix (adding the missing `of_node_put(np)` on the success path) mixed in with the conversion. It might be worth splitting or at least noting in the commit message.

- **Patch 13** (net/bcmgenet): Nice use of `__free(device_node)` cleanup attribute:
```c
+		struct device_node *np __free(device_node) = bcmgenet_mii_of_find_mdio(priv);
+		platform_device_set_of_node(ppdev, np);
```
The `__free(device_node)` ensures the search reference is dropped when `np` goes out of scope, while the helper takes its own ref. Clean.

- **Patches 14-17**: Straightforward conversions of the fixup patches (1-5 sites) to use helpers.

- **Patch 18** (drm/xe/i2c): The DRM-relevant patch. Trivial conversion:
```c
-	pdev->dev.fwnode = fwnode;
+	platform_device_set_fwnode(pdev, fwnode);
```
Since `fwnode` here is a software node (not an OF node), in the pre-patch-23 world this is a no-op behavioral change (the `else` branch of `platform_device_set_fwnode` just does `pdev->dev.fwnode = fwnode`). After patch 23, it will correctly take a fwnode reference. **No issues for the DRM subsystem**.

- **Patch 19** (platform/surface): Same pattern as patch 18 with non-OF fwnode.

- **Patches 20-22**: Convert `device_set_of_node_from_dev()` calls to `platform_device_set_of_node_from_dev()`. The key addition is that fwnode is now synced alongside of_node.

---
Generated by Claude Code Patch Reviewer

  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 Code Review Bot [this message]
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 review: driver core: count references of the platform device's fwnode, not OF node Claude Code Review Bot

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-patch8-20260521-pdev-fwnode-ref-v1-8-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