From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Jie Gan <jie.gan@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 v5] arm64: dts: qcom: glymur: add coresight nodes
Date: Thu, 11 Jun 2026 11:28:52 +0200 [thread overview]
Message-ID: <3c2fdcf8-957b-4b28-85b7-3a50ab8ee485@oss.qualcomm.com> (raw)
In-Reply-To: <20260519-add-coresight-nodes-for-glymur-v5-1-3dad99fe31e0@oss.qualcomm.com>
On 5/19/26 3:14 PM, Jie Gan wrote:
> Add CoreSight nodes to enable trace paths like TPDM->ETF/STM->ETF.
> These devices are part of the AOSS, CDSP, QDSS, PCIe5, TraceNoc and
> some small subsystems, such as GCC, IPCC, PMU and so on.
>
> Delete cti_wpss DT node on Mahua since this device will cause NoC issue
> on Mahua device.
Another good explanation is that it simply doesn't exist there!
> Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>
> ---
[...]
> + tpdm-cdsp-llm {
Nodes without a unit address should be sorted alphabetically
> + compatible = "qcom,coresight-static-tpdm";
> + qcom,cmb-element-bits = <32>;
Do these other TPDMs not have the "DSB element" as the driver
calls it?
> +
> + out-ports {
> + port {
> + cdsp_llm_tpdm_out: endpoint {
> + remote-endpoint = <&cdsp_tpda_in1>;
> + };
> + };
> + };
> + };
> +
> + tpdm-cdsp-llm2 {
> + compatible = "qcom,coresight-static-tpdm";
> + qcom,cmb-element-bits = <32>;
> +
> + out-ports {
> + port {
> + cdsp_llm2_tpdm_out: endpoint {
> + remote-endpoint = <&cdsp_tpda_in2>;
> + };
> + };
> + };
> + };
> +
> + tpdm-cdsp-cmsr {
> + compatible = "qcom,coresight-static-tpdm";
> +
> + qcom,cmb-element-bits = <32>;
> + qcom,dsb-element-bits = <32>;
Some nodes have a \n between compatible and other properties, some don't
Please unify the style (fwiw I prefer the one with a \n)
> base-commit: e98d21c170b01ddef366f023bbfcf6b31509fa83
Please rebase, doesn't apply on next-20260610
Konrad
next prev parent reply other threads:[~2026-06-11 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 13:14 [PATCH v5] arm64: dts: qcom: glymur: add coresight nodes Jie Gan
2026-05-19 13:35 ` sashiko-bot
2026-06-11 9:28 ` Konrad Dybcio [this message]
2026-06-11 23:11 ` Jie Gan
2026-06-16 11:51 ` 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=3c2fdcf8-957b-4b28-85b7-3a50ab8ee485@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jie.gan@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