[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f5d369b7-75ea-406e-a34e-6daa29b54175@amd.com>
Date: Tue, 27 Jan 2026 07:42:56 -0600
From: Mario Limonciello <mario.limonciello@....com>
To: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
Cc: ogabbay@...nel.org, maciej.falkowski@...ux.intel.com,
Hans de Goede <hansg@...nel.org>, Jeff Hugo <jeff.hugo@....qualcomm.com>,
Lizhi Hou <lizhi.hou@....com>, Shyam Sundar S K <Shyam-sundar.S-k@....com>,
dri-devel@...ts.freedesktop.org, LKML <linux-kernel@...r.kernel.org>,
max.zhen@....com, sonal.santan@....com, platform-driver-x86@...r.kernel.org,
VinitKumar.Shukla@....com, Patil Rajesh Reddy <Patil.Reddy@....com>
Subject: Re: [PATCH V4] platform/x86/amd/pmf: Introduce new interface to
export NPU metrics
On 1/27/2026 5:46 AM, Ilpo Järvinen wrote:
> On Mon, 26 Jan 2026, Mario Limonciello wrote:
>
>>
>>
>> On 1/20/2026 8:54 AM, Ilpo Järvinen wrote:
>>> 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.
>>>
>>
>> Lizhi,
>>
>> One clarification. What about the XDNA driver side of this change, are you
>> still going to do it this cycle?
>>
>> If so; this either needs an immutable branch from Ilpo or that side of the
>> change needs to go through pdx86 as well.
>
> Hi Mario,
>
> I was told to me by Lizhi the xdna side patch not going to pursued in
> this cycle [1] so I went with that and changing that now is not realistic
> because of merges I've performed to for-next (I could have easily done
> IB for the change back when applying the patch which would have been the
> default but given that mention, I didn't bother).
>
> [1] https://lore.kernel.org/all/93210832-aa75-7639-c9d2-99ec802d88e4@amd.com/
>
Ah, thanks for confirming, understood.
Powered by blists - more mailing lists