From: Bjorn Andersson <andersson@kernel.org>
To: 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>,
Jie Gan <jie.gan@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: Sun, 5 Jul 2026 15:57:57 -0500 [thread overview]
Message-ID: <178328508291.1157743.10674786439493609885.b4-ty@kernel.org> (raw)
In-Reply-To: <20260414-add-label-to-coresight-device-v2-0-5017d07358f2@oss.qualcomm.com>
On Tue, 14 Apr 2026 19:35:58 +0800, 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
>
> [...]
Applied, thanks!
[1/7] arm64: dts: qcom: lemans: Add label properties to CoreSight devices
commit: 8d52cc232a3c951492a7b90c4172b778d6de1568
[2/7] arm64: dts: qcom: talos: Add label properties to CoreSight devices
commit: 422f5eff44d89367b700235bad829d1430f798a2
[3/7] arm64: dts: qcom: monaco: Add label properties to CoreSight devices
commit: 9ed9c973c6213bb4880fc44dffb266f0330586be
[4/7] arm64: dts: qcom: kodiak: Add label properties to CoreSight devices
commit: d1a21366e880051e453e99aec217dea3e1ffa441
[5/7] arm64: dts: qcom: kaanapali: Add label properties to CoreSight devices
commit: 39a2bf8662412df24ec00378ccdfe667d0529002
[6/7] arm64: dts: qcom: sm8750: Add label properties to CoreSight devices
commit: 9dd195e59a479ff6d605935d78e9e9bc0877bc02
[7/7] arm64: dts: qcom: hamoa: Add label properties to CoreSight devices
commit: 310a5d6a7b65ee161c91bf1cd3a3bf19074275af
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-07-05 20:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 11:35 Jie Gan
2026-04-14 11:35 ` [PATCH v2 1/7] arm64: dts: qcom: lemans: " Jie Gan
2026-04-14 11:36 ` [PATCH v2 2/7] arm64: dts: qcom: talos: " Jie Gan
2026-04-14 11:36 ` [PATCH v2 3/7] arm64: dts: qcom: monaco: " Jie Gan
2026-04-14 11:36 ` [PATCH v2 4/7] arm64: dts: qcom: kodiak: " Jie Gan
2026-04-14 11:36 ` [PATCH v2 5/7] arm64: dts: qcom: kaanapali: " Jie Gan
2026-04-14 11:36 ` [PATCH v2 6/7] arm64: dts: qcom: sm8750: " Jie Gan
2026-04-15 9:11 ` Konrad Dybcio
2026-04-14 11:36 ` [PATCH v2 7/7] arm64: dts: qcom: hamoa: " Jie Gan
2026-05-11 8:17 ` [PATCH v2 0/7] arm64: dts: qcom: " Jie Gan
2026-05-29 10:24 ` Jie Gan
2026-07-05 20:57 ` Bjorn Andersson [this message]
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=178328508291.1157743.10674786439493609885.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jie.gan@oss.qualcomm.com \
--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
all inboxes | Powered by JetHome®