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:24:14 +1000 [thread overview]
Message-ID: <review-overall-20260408130827.2082946-1-andrzej.kacprowski@linux.intel.com> (raw)
In-Reply-To: <20260408130827.2082946-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: 2
Reviewed: 2026-04-12T12:24:14.831269
---
This is a single patch (v2) adding user-configurable NPU frequency limits to the Intel VPU (IVPU) accelerator driver via new sysfs attributes under a `freq/` subdirectory, plus legacy compatibility aliases. The feature is gated behind firmware API 3.34.0 and restricted to 50XX+ generation hardware for the writable attributes.
The overall design is reasonable: a `freq/` group exposes hardware frequency info (read-only) and configurable min/max (read-write for 50XX+), with frequency changes sent to firmware via a new JSM message. However, there are several bugs that need to be fixed before this can be merged.
**Key issues:**
1. Duplicate function declaration (copy-paste error)
2. Wrong sysfs path in ABI documentation (hw_min_freq vs hw_max_freq)
3. Type inconsistency between declaration (u16) and usage (u8)
4. Missing locking for concurrent sysfs writes
5. MHz-to-ratio conversion function is LNL-specific but used generically
6. Cleanup gap: `sysfs_add_file_to_group` files aren't covered by devm
7. Stale/incorrect comment
---
---
Generated by Claude Code Patch Reviewer
next prev parent reply other threads:[~2026-04-12 2:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 13:08 [PATCH v2] accel/ivpu: Add support for limiting NPU frequency Andrzej Kacprowski
2026-04-08 14:14 ` Karol Wachowski
2026-04-12 2:24 ` Claude Code Review Bot [this message]
2026-04-12 2:24 ` Claude review: " Claude Code Review Bot
-- strict thread matches above, loose matches on Subject: below --
2026-04-08 15:01 [PATCH v3] " Andrzej Kacprowski
2026-04-12 2:19 ` Claude review: " Claude Code Review Bot
2026-04-12 2:19 ` 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-20260408130827.2082946-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