From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: accel/amdxdna: Create common SMU interfaces for AIE2 and AIE4
Date: Tue, 31 Mar 2026 17:05:09 +1000 [thread overview]
Message-ID: <review-patch5-20260330163705.3153647-6-lizhi.hou@amd.com> (raw)
In-Reply-To: <20260330163705.3153647-6-lizhi.hou@amd.com>
Patch Review
Moves SMU code from `aie2_smu.c` to `aie_smu.c` with a new `smu_device` abstraction.
**Issue 1 — Non-angle-bracket include:**
```c
+#include "drm/amdxdna_accel.h"
```
Should be `<drm/amdxdna_accel.h>` (angle brackets for installed headers).
**Issue 2 — Unnecessary include:**
```c
+#include <drm/gpu_scheduler.h>
```
`aie_smu.c` doesn't use any gpu_scheduler APIs. This was carried over from the old `aie2_smu.c`.
**Issue 3 — `aie2_smu_fini` wraps two operations but `aie_smu_fini` only does one:**
```c
// Old:
void aie2_smu_fini(struct amdxdna_dev_hdl *ndev)
{
ndev->priv->hw_ops.set_dpm(ndev, 0); // Reset DPM first
aie2_smu_exec(ndev, AIE2_SMU_POWER_OFF, ...);
}
// New wrapper in aie2_pci.c:
static void aie2_smu_fini(struct amdxdna_dev_hdl *ndev)
{
ndev->priv->hw_ops.set_dpm(ndev, 0);
aie_smu_fini(ndev->aie.smu_hdl);
}
```
The DPM reset is kept in the wrapper. This is fine but means AIE4 callers must remember to reset DPM themselves before calling `aie_smu_fini()` or the power-off happens at whatever DPM level was active. The patch 6 AIE4 path calls `aie_smu_fini()` directly without a DPM reset — need to confirm this is intentional.
**Issue 4 — `npu1_set_dpm` moved to `npu1_regs.c`:**
The `npu1_set_dpm` function was `extern` declared in `aie2_pci.h` but is now a `static` function in `npu1_regs.c`. However, `npu4_set_dpm` remains extern. The header still has:
```c
int npu4_set_dpm(struct amdxdna_dev_hdl *ndev, u32 dpm_level);
```
But `npu1_set_dpm` declaration is removed. This works because `npu1_set_dpm` is referenced only via function pointer in `npu1_regs.c`, but the asymmetry is confusing.
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-03-31 7:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 16:36 [PATCH V1 0/6] accel/amdxdna: Initial support for AIE4 platform Lizhi Hou
2026-03-30 16:37 ` [PATCH V1 1/6] accel/amdxdna: Create shared functions for AIE2 and AIE4 Lizhi Hou
2026-03-31 7:05 ` Claude review: " Claude Code Review Bot
2026-03-30 16:37 ` [PATCH V1 2/6] accel/amdxdna: Add basic support for AIE4 devices Lizhi Hou
2026-03-31 7:05 ` Claude review: " Claude Code Review Bot
2026-03-30 16:37 ` [PATCH V1 3/6] accel/amdxdna: Create common PSP interfaces for AIE2 and AIE4 Lizhi Hou
2026-03-31 7:05 ` Claude review: " Claude Code Review Bot
2026-03-30 16:37 ` [PATCH V1 4/6] accel/amdxdna: Add AIE4 firmware loading Lizhi Hou
2026-03-30 20:17 ` Mario Limonciello
2026-03-30 20:30 ` yidong Zhang
2026-03-31 2:45 ` Mario Limonciello
2026-03-31 7:05 ` Claude review: " Claude Code Review Bot
2026-03-30 16:37 ` [PATCH V1 5/6] accel/amdxdna: Create common SMU interfaces for AIE2 and AIE4 Lizhi Hou
2026-03-31 7:05 ` Claude Code Review Bot [this message]
2026-03-30 16:37 ` [PATCH V1 6/6] accel/amdxdna: Add AIE4 power on and off support Lizhi Hou
2026-03-31 7:05 ` Claude review: " Claude Code Review Bot
2026-03-31 7:05 ` Claude review: accel/amdxdna: Initial support for AIE4 platform 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-patch5-20260330163705.3153647-6-lizhi.hou@amd.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