From: Sneh Mankad <sneh.mankad@oss.qualcomm.com>
To: "Maulik Shah (mkshah)" <maulik.shah@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maulik Shah <quic_mkshah@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] soc: qcom: stats: Add stats compatible and config for Shikra
Date: Wed, 8 Jul 2026 20:46:06 +0530 [thread overview]
Message-ID: <916c7405-704a-4487-aa2c-824933ef8837@oss.qualcomm.com> (raw)
In-Reply-To: <91fc1aa6-b237-49e5-be50-87d6a06c6bd6@oss.qualcomm.com>
On 06-Jul-26 2:42 PM, Maulik Shah (mkshah) wrote:
>
>
> On 7/3/2026 4:43 PM, Sneh Mankad wrote:
>> SoC sleep stats are present in RPM message RAM and subsystem sleep
>> stats are present in SMEM for Shikra.
>
> minor nit: use RPM MSGRAM term in above line as well.
>
>>
>> For earlier targets using RPM processor like msm8974, rpm_master_stat.c
>> was used for subsystem sleep stats since those stats were populated in
>> RPM MSGRAM.
>>
>
> [...]
>
>> +---------------|----------------------------|---------------------------+
>> | SoC | subsystem sleep stats | SoC sleep stats |
>> |---------------|----------------------------|---------------------------|
>> | msm8974, | RPM processor MSGRAM | RPM processor MSGRAM |
>> | msm8226 | (rpm_master_stat.c) | (qcom_stats.c) |
>> |---------------|----------------------------|---------------------------|
>> | sm6350, | SMEM (DDR) | AOP processor MSGRAM |
>> | sdm845, etc. | (qcom_stats.c) | (qcom_stats.c) |
>> |---------------|----------------------------|---------------------------|
>> | Shikra | SMEM (DDR) | RPM processor MSGRAM |
>> | | (qcom_stats.c) | (qcom_stats.c) |
>> +---------------|----------------------------|---------------------------+
>>
>
> [...]
>
>>
>> Signed-off-by: Sneh Mankad <sneh.mankad@oss.qualcomm.com>
>
> other than minor nit:, looks good,
Sure, will update.
Thanks,
Sneh
>
> Reviewed-by: Maulik Shah <maulik.shah@oss.qualcomm.com>
>
> Thanks,
> Maulik
next prev parent reply other threads:[~2026-07-08 15:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-03 11:13 [PATCH 0/3] Add subsystem sleep stats support for Shikra Sneh Mankad
2026-07-03 11:13 ` [PATCH 1/3] dt-bindings: soc: qcom: stats: Add compatible " Sneh Mankad
2026-07-06 9:00 ` Maulik Shah (mkshah)
2026-07-06 9:45 ` Konrad Dybcio
2026-07-08 15:13 ` Sneh Mankad
2026-07-03 11:13 ` [PATCH 2/3] soc: qcom: stats: Add stats compatible and config " Sneh Mankad
2026-07-06 9:12 ` Maulik Shah (mkshah)
2026-07-08 15:16 ` Sneh Mankad [this message]
2026-07-06 9:48 ` Konrad Dybcio
2026-07-03 11:13 ` [PATCH 3/3] arm64: dts: qcom: shikra: Add LPM stats support for subsystems Sneh Mankad
2026-07-06 9:23 ` Maulik Shah (mkshah)
2026-07-08 15:15 ` Sneh Mankad
2026-07-06 9:49 ` Konrad Dybcio
2026-07-08 15:12 ` Sneh Mankad
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=916c7405-704a-4487-aa2c-824933ef8837@oss.qualcomm.com \
--to=sneh.mankad@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maulik.shah@oss.qualcomm.com \
--cc=quic_mkshah@quicinc.com \
--cc=robh@kernel.org \
/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