From: Lizhi Hou <lizhi.hou@amd.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>, <ogabbay@kernel.org>,
<quic_jhugo@quicinc.com>, <maciej.falkowski@linux.intel.com>,
Hans de Goede <hansg@kernel.org>,
<dri-devel@lists.freedesktop.org>,
LKML <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 V3 1/2] platform/x86/amd/pmf: Introduce new interface to export NPU metrics
Date: Tue, 6 Jan 2026 09:35:04 -0800 [thread overview]
Message-ID: <93210832-aa75-7639-c9d2-99ec802d88e4@amd.com> (raw)
In-Reply-To: <b6c80015-d399-e8c1-4b8a-d2ebb4cee9da@linux.intel.com>
On 1/6/26 09:09, Ilpo Järvinen wrote:
> On Tue, 6 Jan 2026, Lizhi Hou wrote:
>
>> What should be the next step? Should I generate both patches based on
>> review-ilpo-next? Will the amdxdna change upstream through platform-x86 tree?
> (We seemed to have crossed emails.)
>
> That would work for me too, but I thought it was wanted that patch 2 to
> go through accel?
Thanks a lot. Glad to know patch 1 is good and I will not post another
one. :)
The patch 2 depends on patch1. I agree that patch 2 to go through accel
which can avoid conflict with other recent amdxdna driver changes. So I
can wait the patch 1 to be upstream and reach to drm-misc, then submit
patch 2 there. Does it sound a right plan?
Thanks,
Lizhi
>
next prev parent reply other threads:[~2026-01-06 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 17:29 [PATCH V3 0/2] Get real time power input via AMD PMF Lizhi Hou
2026-01-05 17:29 ` [PATCH V3 1/2] platform/x86/amd/pmf: Introduce new interface to export NPU metrics Lizhi Hou
2026-01-06 13:19 ` Shyam Sundar S K
2026-01-06 16:16 ` Lizhi Hou
2026-01-06 17:05 ` Ilpo Järvinen
2026-01-06 17:07 ` Lizhi Hou
2026-01-06 17:09 ` Ilpo Järvinen
2026-01-06 17:35 ` Lizhi Hou [this message]
2026-01-15 15:18 ` Ilpo Järvinen
2026-01-15 16:49 ` Lizhi Hou
2026-01-05 17:29 ` [PATCH V3 2/2] accel/amdxdna: Add IOCTL to retrieve realtime NPU power estimate Lizhi Hou
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=93210832-aa75-7639-c9d2-99ec802d88e4@amd.com \
--to=lizhi.hou@amd.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=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
all inboxes | Powered by JetHome®