From: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
To: Sneh Mankad <sneh.mankad@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 v4 1/3] dt-bindings: soc: qcom: stats: Add compatible for Shikra
Date: Sun, 13 Sep 2026 23:40:36 +0530 [thread overview]
Message-ID: <44dde4c9-e4f1-498e-8247-94e03e85c521@oss.qualcomm.com> (raw)
In-Reply-To: <20260907-shikra_stats-v4-1-3825351f9740@oss.qualcomm.com>
On 9/7/2026 7:17 PM, Sneh Mankad wrote:
> SoC LPM stats are present in RPM MSGRAM and subsystem LPM stats are present
> in SMEM for Shikra.
>
> A generic "qcom,rpm-stats" compatible only reads SoC LPM stats like vmin
> and vlow.
>
> Document shikra rpm compatible to read subsystem LPM stats too along with
> SoC LPM stats.
>
> Keep "qcom,rpm-stats" as a fallback for RPM targets, so that SoC level
> stats are still shown even without subsystem level stats support. A plain
> enum can't express that, since it caps compatible at one item. Add a oneOf
> branch with items for this pattern.
>
> Signed-off-by: Sneh Mankad <sneh.mankad@oss.qualcomm.com>
Reviewed-by: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
next prev parent reply other threads:[~2026-09-13 18:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 13:47 [PATCH v4 0/3] Add subsystem LPM stats support " Sneh Mankad
2026-09-07 13:47 ` [PATCH v4 1/3] dt-bindings: soc: qcom: stats: Add compatible " Sneh Mankad
2026-09-13 18:10 ` Komal Bajaj [this message]
2026-09-07 13:47 ` [PATCH v4 2/3] soc: qcom: stats: Add stats compatible and config " Sneh Mankad
2026-09-13 18:11 ` Komal Bajaj
2026-09-14 13:57 ` Abel Vesa
2026-09-07 13:47 ` [PATCH v4 3/3] arm64: dts: qcom: shikra: Update rpm-stats compatible to SoC specific Sneh Mankad
2026-09-13 18:11 ` Komal Bajaj
2026-09-14 13:58 ` 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=44dde4c9-e4f1-498e-8247-94e03e85c521@oss.qualcomm.com \
--to=komal.bajaj@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=quic_mkshah@quicinc.com \
--cc=robh@kernel.org \
--cc=sneh.mankad@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®