From: Navya Malempati <navya.malempati@oss.qualcomm.com>
To: Pankaj Patil <pankaj.patil@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: qcom: qcom_stats: Add support for NSP subsystem stats
Date: Tue, 15 Sep 2026 09:39:56 +0530 [thread overview]
Message-ID: <208b9e11-d36e-4376-9836-ce9ed3c81486@oss.qualcomm.com> (raw)
In-Reply-To: <4f518cb0-ed7b-4c2c-9a79-8d1549b26428@oss.qualcomm.com>
On 9/8/2026 3:33 PM, Pankaj Patil wrote:
> On 9/8/2026 1:43 PM, Navya Malempati wrote:
>> Add SMEM items for four NSP subsystems stats which are present in Nord
>> SoC. Rename CDSP stats as CDSP_NSP as both use same PID and SMEM item
>> id. Add new entries for NSP1/2/3.
>
> For other targets as well is the same applicable? NSP and CDSP are interchangeable?
>
From the stats point of view, they are the same, we used the name NSP
in downstream, it looks like Nord SoC remoteproc is using the name CDSP [1]
[1]
https://lore.kernel.org/linux-arm-msm/20260904081619.593602-2-shengchao.guo@oss.qualcomm.com/
>>
>> Signed-off-by: Navya Malempati <navya.malempati@oss.qualcomm.com>
>> ---
>> drivers/soc/qcom/qcom_stats.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/soc/qcom/qcom_stats.c b/drivers/soc/qcom/qcom_stats.c
>> index 06923408bfce..91f2d1293124 100644
>> --- a/drivers/soc/qcom/qcom_stats.c
>> +++ b/drivers/soc/qcom/qcom_stats.c
>> @@ -43,8 +43,11 @@ static const struct subsystem_data subsystems[] = {
>> { "modem", 605, 1 },
>> { "wpss", 605, 13 },
>> { "adsp", 606, 2 },
>> - { "cdsp", 607, 5 },
>> + { "cdsp_nsp", 607, 5 },
>> { "cdsp1", 607, 12 },
>
> Is cdsp1 not the same as nsp1?
No, cdsp1 is not the same as nsp1.
> Adding cdsp_nsp_1 is very SOC specific
>
No, this is not a SoC specific setting.
Thanks,
Navya
next prev parent reply other threads:[~2026-09-15 4:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 8:13 Navya Malempati
2026-09-08 10:03 ` Pankaj Patil
2026-09-15 4:09 ` Navya Malempati [this message]
2026-09-18 8:34 ` Konrad Dybcio
2026-09-21 15:27 ` Pankaj Patil
2026-10-01 10:21 ` Navya Malempati
2026-10-01 10:20 ` Navya Malempati
2026-09-15 11:24 ` Maulik Shah
2026-09-15 12:50 ` Abel Vesa
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=208b9e11-d36e-4376-9836-ce9ed3c81486@oss.qualcomm.com \
--to=navya.malempati@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.patil@oss.qualcomm.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®