From: Jeff Hugo <jeff.hugo@oss.qualcomm.com>
To: Andrzej Kacprowski <andrzej.kacprowski@linux.intel.com>,
dri-devel@lists.freedesktop.org
Cc: oded.gabbay@gmail.com, karol.wachowski@linux.intel.com,
lizhi.hou@amd.com, maciej.falkowski@linux.intel.com
Subject: Re: [PATCH] accel/ivpu: Add support for limiting NPU frequency
Date: Tue, 31 Mar 2026 00:12:43 -0600 [thread overview]
Message-ID: <dcf02dcc-e49f-4d7a-8cec-95d177b32336@oss.qualcomm.com> (raw)
In-Reply-To: <20260330083815.1806045-1-andrzej.kacprowski@linux.intel.com>
On 3/30/2026 2:38 AM, Andrzej Kacprowski wrote:
> Add configurable frequency limits to allow users to constrain the NPU
> operating frequency range for power and thermal management. This support
> requires firmware API version 3.34.0 or newer.
>
> New sysfs interface:
>
> The freq/ subdirectory contains the following attributes:
>
> - hw_min_freq: Minimum frequency supported by hardware (read-only)
> - hw_max_freq: Maximum frequency supported by hardware (read-only)
> - hw_efficient_freq: Hardware's optimal operating frequency (read-only)
> - current_freq: Current NPU frequency in MHz (read-only)
> - set_min_freq: Configure minimum operating frequency (50XX+ devices)
> - set_max_freq: Configure maximum operating frequency (50XX+ devices)
I don't see Documentation/ABI changes in this patch, which are required
for sysfs.
However, I wonder if this is the best way to move forward. At best, you
appear to be implementing a completely custom version of hwmon. However,
I wonder if hwmon/sysfs will be limiting as you support 3 generations of
devices if I recall correctly, and that number is probably going to go
up. With the different generations supporting different capabilities, I
suspect the sysfs approach will eventually put you into a corner.
Your collegues over in the XE area have proposed a netlink mechanism,
which is in -next currently (expected to go in the 7.1 merge window). We
collaborated on that mechanism, and have plans to extend it for these
kinds of "telemetry" items. I'm expecting we'll have some patches posted
on list in a week, maybe 2 (finishing up some of the final details).
Perhaps you would find that useful?
-Jeff
next prev parent reply other threads:[~2026-03-31 6:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 8:38 [PATCH] accel/ivpu: Add support for limiting NPU frequency Andrzej Kacprowski
2026-03-31 6:12 ` Jeff Hugo [this message]
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=dcf02dcc-e49f-4d7a-8cec-95d177b32336@oss.qualcomm.com \
--to=jeff.hugo@oss.qualcomm.com \
--cc=andrzej.kacprowski@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=karol.wachowski@linux.intel.com \
--cc=lizhi.hou@amd.com \
--cc=maciej.falkowski@linux.intel.com \
--cc=oded.gabbay@gmail.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