The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Lizhi Hou <lizhi.hou@amd.com>
To: Mario Limonciello <mario.limonciello@amd.com>,
	<ilpo.jarvinen@linux.intel.com>, <hansg@kernel.org>,
	<ogabbay@kernel.org>, <quic_jhugo@quicinc.com>,
	<maciej.falkowski@linux.intel.com>
Cc: <linux-kernel@vger.kernel.org>, <max.zhen@amd.com>,
	<sonal.santan@amd.com>, <platform-driver-x86@vger.kernel.org>,
	<dri-devel@lists.freedesktop.org>, <Shyam-sundar.S-k@amd.com>,
	<VinitKumar.Shukla@amd.com>
Subject: Re: [PATCH V1 0/2] Get real time power input via AMD PMF
Date: Thu, 11 Dec 2025 11:16:19 -0800	[thread overview]
Message-ID: <1b4e61c5-bf4b-4044-0dbf-bb16a331d8bc@amd.com> (raw)
In-Reply-To: <a77c3b39-49e2-481f-af53-70b5fbe58ffd@amd.com>


On 12/11/25 10:22, Mario Limonciello wrote:
> On 12/11/25 11:58 AM, Lizhi Hou wrote:
>> Adding new NPU metrics API to AMD PMF driver is pending because of
>> lacking real case.
>> https://lore.kernel.org/all/d344b850-f68d-f9a5-f0dc-55af4b48b714@linux.intel.com/
>>
>> Create xdna driver patch to fetch real time power input via PMF API.
>> Here is an example output with xrt-smi(1) tool.
>>
>> # xrt-smi examine -r all | grep Power
>>    Power Mode             : Default
>> Estimated Power          : 0.563 Watts
>>
>> Lizhi Hou (1):
>>    accel/amdxdna: Add IOCTL to retrieve realtime NPU power estimate
>>
>> Shyam Sundar S K (1):
>>    platform/x86/amd/pmf: Introduce new interface to export NPU metrics
>>
>>   drivers/accel/amdxdna/aie2_pci.c        | 29 ++++++++++
>>   drivers/accel/amdxdna/aie2_pci.h        | 18 ++++++
>>   drivers/accel/amdxdna/amdxdna_pci_drv.c |  3 +-
>>   drivers/platform/x86/amd/pmf/core.c     | 75 +++++++++++++++++++++++++
>>   drivers/platform/x86/amd/pmf/pmf.h      |  2 +
>>   include/linux/amd-pmf-io.h              | 21 +++++++
>>   6 files changed, 147 insertions(+), 1 deletion(-)
>>
>
> Do you have a preference on how this gets merged ? Should it go 
> through drm-next or platform-x86-next?
>
> I suppose whoever is going to have more development layering on top 
> the next cycle it would be preferable to put in that tree.

I do not have preference. :) And this depends on Shyam's previous patch 
which is not in drm-next yet?

Thanks,

Lizhi


      reply	other threads:[~2025-12-11 19:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-11 17:58 [PATCH V1 0/2] Get real time power input via AMD PMF Lizhi Hou
2025-12-11 17:58 ` [PATCH V1 1/2] platform/x86/amd/pmf: Introduce new interface to export NPU metrics Lizhi Hou
2025-12-11 18:28   ` Ilpo Järvinen
2025-12-11 19:07     ` Lizhi Hou
2025-12-12  6:00     ` Shyam Sundar S K
2025-12-11 17:58 ` [PATCH V2 2/2] accel/amdxdna: Add IOCTL to retrieve realtime NPU power estimate Lizhi Hou
2025-12-11 18:20   ` Mario Limonciello
2025-12-11 18:24   ` Ilpo Järvinen
2025-12-11 19:06     ` Lizhi Hou
2025-12-12  6:01   ` Shyam Sundar S K
2025-12-11 18:22 ` [PATCH V1 0/2] Get real time power input via AMD PMF Mario Limonciello
2025-12-11 19:16   ` Lizhi Hou [this message]

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=1b4e61c5-bf4b-4044-0dbf-bb16a331d8bc@amd.com \
    --to=lizhi.hou@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=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --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=quic_jhugo@quicinc.com \
    --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