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: accel/ivpu: Add support for limiting NPU frequency
Date: Sun, 12 Apr 2026 12:19:40 +1000	[thread overview]
Message-ID: <review-overall-20260408150152.2093638-1-andrzej.kacprowski@linux.intel.com> (raw)
In-Reply-To: <20260408150152.2093638-1-andrzej.kacprowski@linux.intel.com>

Overall Series Review

Subject: accel/ivpu: Add support for limiting NPU frequency
Author: Andrzej Kacprowski <andrzej.kacprowski@linux.intel.com>
Patches: 1
Reviewed: 2026-04-12T12:19:40.349981

---

This is a single-patch series (v3) adding configurable NPU frequency limits to the Intel IVPU accelerator driver. The feature introduces a new `freq/` sysfs subdirectory with hardware info and configurable min/max frequency attributes, a new JSM firmware message (`VPU_JSM_MSG_FREQ_CONFIG`), and legacy compatibility aliases for the existing top-level sysfs frequency attributes.

The overall design is reasonable: a `freq/` group for organized frequency attributes, firmware communication via JSM messages, and conditional exposure of writable attributes only on 50XX+ devices. The code is generally clean and follows existing driver patterns. However, there are several issues ranging from a type mismatch bug to missing access controls and cleanup concerns.

**Key issues:**
1. **Type mismatch between function signature and internal callers** (`u16` in declaration vs `u8` at call sites and `u32` in payload struct)
2. **No permission check on writable sysfs attributes** — any user can change NPU frequency
3. **Missing concurrency protection** for `cfg_min_ratio`/`cfg_max_ratio`
4. **Misleading comment** in `set_max_freq_store`
5. **`dpu_mhz_to_pll_ratio_lnl` used unconditionally** for MTL devices too
6. **Sysfs cleanup not handled** for manually-added files

---

---
Generated by Claude Code Patch Reviewer

  reply	other threads:[~2026-04-12  2:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-08 15:01 [PATCH v3] accel/ivpu: Add support for limiting NPU frequency Andrzej Kacprowski
2026-04-12  2:19 ` Claude Code Review Bot [this message]
2026-04-12  2:19 ` Claude review: " Claude Code Review Bot
  -- strict thread matches above, loose matches on Subject: below --
2026-04-08 13:08 [PATCH v2] " Andrzej Kacprowski
2026-04-12  2:24 ` Claude review: " Claude Code Review Bot
2026-04-12  2:24 ` Claude Code Review Bot
2026-03-30  8:38 [PATCH] " Andrzej Kacprowski
2026-03-31  7:27 ` Claude review: " Claude Code Review Bot
2026-03-31  7:27 ` 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-overall-20260408150152.2093638-1-andrzej.kacprowski@linux.intel.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