From: Jie Gan <jie.gan@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@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>,
Tingwei Zhang <tingwei.zhang@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: qcom: dts: sm8750: add coresight nodes
Date: Wed, 19 Nov 2025 10:01:57 +0800 [thread overview]
Message-ID: <cfd9867a-5fa5-43f1-a1a7-81f05bacc47f@oss.qualcomm.com> (raw)
In-Reply-To: <350ddcc0-cbab-4b58-8b50-5004f27688db@oss.qualcomm.com>
On 11/18/2025 6:03 PM, Konrad Dybcio wrote:
> On 11/17/25 10:31 AM, Jie Gan wrote:
>> Add CoreSight DT nodes for AOSS, QDSS, Turing, and Modem blocks to enable
>> the STM and TPDM sources to route trace data to the ETF for debugging.
>>
>> Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>
>> ---
>> arch/arm64/boot/dts/qcom/sm8750.dtsi | 981 +++++++++++++++++++++++++++++++++++
>> 1 file changed, 981 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/sm8750.dtsi b/arch/arm64/boot/dts/qcom/sm8750.dtsi
>> index 3f0b57f428bb..56c2605f3e0d 100644
>> --- a/arch/arm64/boot/dts/qcom/sm8750.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/sm8750.dtsi
>> @@ -3313,6 +3313,948 @@ tcsrcc: clock-controller@f204008 {
>> #reset-cells = <1>;
>> };
>>
>> + stm@10002000 {
>> + compatible = "arm,coresight-stm", "arm,primecell";
>> + reg = <0x0 0x10002000 0x0 0x1000>,
>> + <0x0 0x37280000 0x0 0x180000>;
>
> This region is a little bigger but it's not described clearly. Is there
> a reason to use this slice of it and not the whole thing?
This region is about the STM channels which are allocated for APSS/HLOS.
The channel 10240-20479 is allocated for APSS/HLOS, each occupied 256.
So the start address is 10240 * 256 = 2,621,440 (0x28000). The length is
0x180000 because we only use part of these channels so far.
>
> [...]
>
>> + funnel_in0_in0: endpoint {
>> + remote-endpoint =
>> + <&tn_ag_out>;
>
> Please unwrap this line
Will fix it.
>
> [...]
>
>
>> + tn@109ab000 {
>> + compatible = "qcom,coresight-tnoc", "arm,primecell";
>
> "tnoc@"?
In dt-binding, we suggested tn, it also could be tnoc here.
>
> [...]
>
>
>> + tpdm_llm {
>
> Node names still can't include underscores ;)
Sure, missed this part, will fix.
>
> Please also rename 'llm' and 'turing' to 'cdsp' unless there's a good
> reason not to
>
Will fix.
> I confirmed the coresight components addresses match their claimed function
Thanks for checking, it's a huge effort.
Thanks,
Jie
>
> Konrad
next prev parent reply other threads:[~2025-11-19 2:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 9:31 [PATCH] arm64: qcom: dts: sm8750: add coresight nodes Jie Gan
2025-11-18 10:03 ` Konrad Dybcio
2025-11-19 2:01 ` Jie Gan [this message]
2025-11-19 14:06 ` Konrad Dybcio
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=cfd9867a-5fa5-43f1-a1a7-81f05bacc47f@oss.qualcomm.com \
--to=jie.gan@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=tingwei.zhang@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;
as well as URLs for NNTP newsgroup(s).