From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: ogabbay@kernel.org, maciej.falkowski@linux.intel.com,
hansg@kernel.org, Jeff Hugo <jeff.hugo@oss.qualcomm.com>,
Lizhi Hou <lizhi.hou@amd.com>
Cc: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
max.zhen@amd.com, sonal.santan@amd.com,
mario.limonciello@amd.com, platform-driver-x86@vger.kernel.org,
VinitKumar.Shukla@amd.com,
Patil Rajesh Reddy <Patil.Reddy@amd.com>
Subject: Re: [PATCH V4] platform/x86/amd/pmf: Introduce new interface to export NPU metrics
Date: Tue, 20 Jan 2026 16:54:05 +0200 [thread overview]
Message-ID: <176892084537.15580.12089679537024504744.b4-ty@linux.intel.com> (raw)
In-Reply-To: <20260115173448.403826-1-lizhi.hou@amd.com>
On Thu, 15 Jan 2026 09:34:48 -0800, Lizhi Hou wrote:
> The PMF driver retrieves NPU metrics data from the PMFW. Introduce a new
> interface to make NPU metrics accessible to other drivers like AMDXDNA
> driver, which can access and utilize this information as needed.
>
>
Thank you for your contribution, it has been applied to my local
review-ilpo-next branch. Note it will show up in the public
platform-drivers-x86/review-ilpo-next branch only once I've pushed my
local branch there, which might take a while.
The list of commits applied:
[1/1] platform/x86/amd/pmf: Introduce new interface to export NPU metrics
commit: 15e19bd95be5c79f2f98b727edda002ba86f8d03
--
i.
next prev parent reply other threads:[~2026-01-20 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 17:34 [PATCH V4] platform/x86/amd/pmf: Introduce new interface to export NPU metrics Lizhi Hou
2026-01-20 14:54 ` Ilpo Järvinen [this message]
2026-01-27 5:04 ` Mario Limonciello
2026-01-27 11:46 ` Ilpo Järvinen
2026-01-27 13:42 ` Mario Limonciello
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=176892084537.15580.12089679537024504744.b4-ty@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Patil.Reddy@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=VinitKumar.Shukla@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hansg@kernel.org \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.hou@amd.com \
--cc=maciej.falkowski@linux.intel.com \
--cc=mario.limonciello@amd.com \
--cc=max.zhen@amd.com \
--cc=ogabbay@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=sonal.santan@amd.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