From: Caleb Connolly <caleb.connolly@linaro.org>
To: Abel Vesa <abel.vesa@linaro.org>, Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Maulik Shah <quic_mkshah@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/4] arm64: dts: qcom: sdm845: Add the RPMh stats node
Date: Mon, 15 Aug 2022 21:34:07 +0100 [thread overview]
Message-ID: <e6821eef-4fcb-97b1-24be-e2bb62b99039@linaro.org> (raw)
In-Reply-To: <20220812101240.1869605-3-abel.vesa@linaro.org>
On 12/08/2022 11:12, Abel Vesa wrote:
> SDM845 is a special case compared to the other platforms that use RPMh
> stats, since it only has 2 stats (aosd and cxsd), while the others have
> a 3rd one (ddr).
>
> So lets add the node but with a SDM845 dedicated compatible to make
> the driver aware of the different stats config.
Hi,
I gave this a go on the OnePlus 6, I noticed the driver is also meant to read
the stats for remote procs via smem, however this seems to fail for me - it
can't find any of the SMEM items even if I probe the driver manually after
ensuring remoteprocs have booted. Is this an unsupported feature on SDM845?
>
> Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
> ---
>
> Changed qcom,rpmh-stats-sdm845 to qcom,sdm845-rpmh-stats, as suggested
> by Krzysztof.
>
> arch/arm64/boot/dts/qcom/sdm845.dtsi | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi b/arch/arm64/boot/dts/qcom/sdm845.dtsi
> index 5bea96a9ce06..67fe08b837be 100644
> --- a/arch/arm64/boot/dts/qcom/sdm845.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sdm845.dtsi
> @@ -4851,6 +4851,11 @@ ebi_cdev: ebi {
> };
> };
>
> + sram@c3f0000 {
> + compatible = "qcom,sdm845-rpmh-stats";
> + reg = <0 0x0c3f0000 0 0x400>;
> + };
> +
> spmi_bus: spmi@c440000 {
> compatible = "qcom,spmi-pmic-arb";
> reg = <0 0x0c440000 0 0x1100>,
> --
> 2.34.1
>
--
Kind Regards,
Caleb (they/he)
next prev parent reply other threads:[~2022-08-16 0:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 10:12 [PATCH v2 1/4] arm64: dts: qcom: sdm845: Reduce reg size for aoss_qmp Abel Vesa
2022-08-12 10:12 ` [PATCH v2 2/4] soc: qcom: stats: Add SDM845 stats config and compatible Abel Vesa
2022-08-12 10:17 ` Krzysztof Kozlowski
2022-08-12 10:12 ` [PATCH v2 3/4] arm64: dts: qcom: sdm845: Add the RPMh stats node Abel Vesa
2022-08-12 10:17 ` Krzysztof Kozlowski
2022-08-15 20:34 ` Caleb Connolly [this message]
2022-08-16 10:30 ` Abel Vesa
2022-08-16 13:50 ` Caleb Connolly
2022-08-16 15:32 ` Abel Vesa
2022-08-18 1:47 ` Bjorn Andersson
2022-08-18 6:01 ` Abel Vesa
2022-08-12 10:12 ` [PATCH v2 4/4] dt-bindings: soc: qcom: stats: Document SDM845 compatible Abel Vesa
2022-08-12 10:17 ` Krzysztof Kozlowski
2022-08-12 10:17 ` [PATCH v2 1/4] arm64: dts: qcom: sdm845: Reduce reg size for aoss_qmp Krzysztof Kozlowski
2022-08-29 23:45 ` (subset) " Bjorn Andersson
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=e6821eef-4fcb-97b1-24be-e2bb62b99039@linaro.org \
--to=caleb.connolly@linaro.org \
--cc=abel.vesa@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_mkshah@quicinc.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;
as well as URLs for NNTP newsgroup(s).