public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
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 2/7] arm64: dts: qcom: talos: Add label properties to CoreSight devices
Date: Tue, 14 Apr 2026 12:04:57 +0200	[thread overview]
Message-ID: <717c4b3b-426b-4e1a-b910-af466f8ef2b4@oss.qualcomm.com> (raw)
In-Reply-To: <20260410-add-label-to-coresight-device-v1-2-d71a6759dbc2@oss.qualcomm.com>

On 4/10/26 5:08 AM, Jie Gan wrote:
> Add label properties to CTI and TPDM nodes in the talos device tree to
> provide human-readable identifiers for each CoreSight device. These
> labels allow userspace tools and the CoreSight framework to identify
> devices by name rather than by base address.
> 
> Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>
> ---

Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>

Konrad3597,6 +3652,7 @@ tpdm@78b0000 {>  
>  			clocks = <&aoss_qmp>;
>  			clock-names = "apb_pclk";
> +			label = "tpdm_llm_gold";
>  
>  			qcom,cmb-element-bits = <32>;
>  			qcom,cmb-msrs-num = <32>;
> @@ -3664,6 +3720,7 @@ cti@78e0000 {
>  
>  			clocks = <&aoss_qmp>;
>  			clock-names = "apb_pclk";
> +			label = "cti_apss";
>  		};
>  
>  		cti@78f0000 {
> @@ -3672,6 +3729,7 @@ cti@78f0000 {
>  
>  			clocks = <&aoss_qmp>;
>  			clock-names = "apb_pclk";
> +			label = "cti_apss_1";
>  		};
>  
>  		cti@7900000 {
> @@ -3680,6 +3738,7 @@ cti@7900000 {
>  
>  			clocks = <&aoss_qmp>;
>  			clock-names = "apb_pclk";
> +			label = "cti_apss_2";
>  		};
>  
>  		remoteproc_cdsp: remoteproc@8300000 {
> 

  reply	other threads:[~2026-04-14 10:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10  3:08 [PATCH 0/7] arm64: dts: qcom: Add label properties to CoreSight devices Jie Gan
2026-04-10  3:08 ` [PATCH 1/7] arm64: dts: qcom: lemans: " Jie Gan
2026-04-14  9:59   ` Konrad Dybcio
2026-04-10  3:08 ` [PATCH 2/7] arm64: dts: qcom: talos: " Jie Gan
2026-04-14 10:04   ` Konrad Dybcio [this message]
2026-04-10  3:08 ` [PATCH 3/7] arm64: dts: qcom: monaco: " Jie Gan
2026-04-14 10:09   ` Konrad Dybcio
2026-04-10  3:08 ` [PATCH 4/7] arm64: dts: qcom: kodiak: " Jie Gan
2026-04-14 10:11   ` Konrad Dybcio
2026-04-10  3:08 ` [PATCH 5/7] arm64: dts: qcom: kaanapali: " Jie Gan
2026-04-14 10:15   ` Konrad Dybcio
2026-04-10  3:08 ` [PATCH 6/7] arm64: dts: qcom: sm8750: " Jie Gan
2026-04-14 10:19   ` Konrad Dybcio
2026-04-14 11:29     ` Jie Gan
2026-04-10  3:08 ` [PATCH 7/7] arm64: dts: qcom: hamoa: " Jie Gan
2026-04-14 10:22   ` 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=717c4b3b-426b-4e1a-b910-af466f8ef2b4@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