From: Jie Gan <jie.gan@oss.qualcomm.com>
To: 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,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v2 0/7] arm64: dts: qcom: Add label properties to CoreSight devices
Date: Mon, 11 May 2026 16:17:08 +0800 [thread overview]
Message-ID: <6dd0c0f4-9c40-4e7c-ba4c-e6e86f1fc95a@oss.qualcomm.com> (raw)
In-Reply-To: <20260414-add-label-to-coresight-device-v2-0-5017d07358f2@oss.qualcomm.com>
On 4/14/2026 7:35 PM, Jie Gan wrote:
> The CoreSight framework and userspace tools identify trace devices by
> their base address, which is not human-readable. The label property
> provides a stable, descriptive name for each TPDM and CTI device,
> allowing tools to refer to devices by name rather than address.
>
> This series adds label properties to TPDM and CTI nodes across seven
> Qualcomm platforms:
> lemans
> talos
> monaco
> kodiak
> kaanapali
> sm8750
> hamoa
>
> With the change, we will have a sysfs node for each Coresight device:
> root@qemuarm64:/sys/bus/coresight/devices/tpdm0# cat label
> tpdm_spdm
>
Gentle reminder.
> Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>
> ---
> Changes in v2:
> - fix the extra tab format issue in patch 6 (sm8750).
> - Link to v1: https://lore.kernel.org/r/20260410-add-label-to-coresight-device-v1-0-d71a6759dbc2@oss.qualcomm.com
>
> ---
> Jie Gan (7):
> arm64: dts: qcom: lemans: Add label properties to CoreSight devices
> arm64: dts: qcom: talos: Add label properties to CoreSight devices
> arm64: dts: qcom: monaco: Add label properties to CoreSight devices
> arm64: dts: qcom: kodiak: Add label properties to CoreSight devices
> arm64: dts: qcom: kaanapali: Add label properties to CoreSight devices
> arm64: dts: qcom: sm8750: Add label properties to CoreSight devices
> arm64: dts: qcom: hamoa: Add label properties to CoreSight devices
>
> arch/arm64/boot/dts/qcom/hamoa.dtsi | 30 +++++++++++++++++
> arch/arm64/boot/dts/qcom/kaanapali.dtsi | 35 +++++++++++++++++++
> arch/arm64/boot/dts/qcom/kodiak.dtsi | 12 +++++++
> arch/arm64/boot/dts/qcom/lemans.dtsi | 14 ++++++++
> arch/arm64/boot/dts/qcom/monaco.dtsi | 29 ++++++++++++++++
> arch/arm64/boot/dts/qcom/sm8750.dtsi | 27 +++++++++++++++
> arch/arm64/boot/dts/qcom/talos.dtsi | 59 +++++++++++++++++++++++++++++++++
> 7 files changed, 206 insertions(+)
> ---
> base-commit: f3e6330d7fe42b204af05a2dbc68b379e0ad179e
> change-id: 20260409-add-label-to-coresight-device-b17a2ba6030e
>
> Best regards,
parent reply other threads:[~2026-05-11 8:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20260414-add-label-to-coresight-device-v2-0-5017d07358f2@oss.qualcomm.com>]
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=6dd0c0f4-9c40-4e7c-ba4c-e6e86f1fc95a@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