From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Jie Gan <jie.gan@oss.qualcomm.com>,
Mike Leach <mike.leach@linaro.org>,
James Clark <james.clark@linaro.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>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
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 v3 0/3] Enable CTCU and ETR devices for multiple QCOM platforms
Date: Fri, 29 May 2026 12:10:23 +0100 [thread overview]
Message-ID: <6b7294a1-8c13-42aa-9f64-5b5c9af0b41f@arm.com> (raw)
In-Reply-To: <f2f23d0a-dc24-4a06-948d-56df913994ba@oss.qualcomm.com>
On 29/05/2026 11:26, Jie Gan wrote:
>
>
> On 2/27/2026 6:10 PM, Suzuki K Poulose wrote:
>> Hello,
>>
>>
>> On 04/02/2026 02:22, Jie Gan wrote:
>>> The DT‑binding patch adds platform‑specific compatibles for the
>>> CTCU device, and the following Qualcomm platforms are included:
>>> Kaanapali
>>> Pakala(sm8750)
>>> Hamoa(x1e80100)
>>> Glymur
>>
>> Given this is predominantly DTS changes, and there is very low chances
>> of a conflict with the binding yaml change, I would recommend this to go
>> via soc or the qcom platform tree.
>>
>> For the series:
>>
>> Acked-by: Suzuki K Poulose <suzuki.poulose@arm.com>
>
> Hi Suzuki,
>
> May I ask is there a chance this patch series could go through the
> CoreSight tree?
Like I said, it is mostly Qcom platform changes. So, I would leave it to
the appropriate channel
Suzuki
>
> Thanks a lot.
> Jie
>
>>
>>
>>>
>>> Since the base Coresight DT patches for the Kaanapali and Glymur
>>> platforms have not yet been applied, I created DT patches only
>>> for the Pakala and Hamoa platforms. I will submit the Kaanapali
>>> and Glymur patches once their corresponding base Coresight DT patches
>>> are merged.
>>>
>>> The Hamoa‑related patches were posted in a separate email, and I
>>> have included them in the current patch series.
>>>
>>> Link to the previous Hamoa patch series:
>>> https://lore.kernel.org/all/20251106-enable-etr-and-ctcu-for-hamoa-
>>> v2-0-cdb3a18753aa@oss.qualcomm.com/
>>>
>>> Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>
>>> ---
>>> Changes in v3:
>>> - change back to the numeric compatible from hamoa to x1e80100.
>>> - Link to v2: https://lore.kernel.org/r/20260203-enable-ctcu-and-etr-
>>> v2-0-aacc7bd7eccb@oss.qualcomm.com
>>>
>>> Changes in v2:
>>> - change back to the numeric compatible from pakala to sm8750.
>>> - Link to v1: https://lore.kernel.org/r/20260203-enable-ctcu-and-etr-
>>> v1-0-a5371a2ec2b8@oss.qualcomm.com
>>>
>>> ---
>>> Jie Gan (3):
>>> dt-binding: document QCOM platforms for CTCU device
>>> arm64: dts: qcom: hamoa: enable ETR and CTCU devices
>>> arm64: dts: qcom: sm8750: enable ETR and CTCU devices
>>>
>>> .../bindings/arm/qcom,coresight-ctcu.yaml | 4 +
>>> arch/arm64/boot/dts/qcom/hamoa.dtsi | 160 ++++++++++
>>> + +++++++-
>>> arch/arm64/boot/dts/qcom/sm8750.dtsi | 177 ++++++++++
>>> + ++++++++++
>>> 3 files changed, 340 insertions(+), 1 deletion(-)
>>> ---
>>> base-commit: 193579fe01389bc21aff0051d13f24e8ea95b47d
>>> change-id: 20260203-enable-ctcu-and-etr-31f9e9d1088d
>>>
>>> Best regards,
>>
>
next prev parent reply other threads:[~2026-05-29 11:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 2:22 [PATCH v3 0/3] Enable CTCU and ETR devices for multiple QCOM platforms Jie Gan
2026-02-04 2:22 ` [PATCH v3 1/3] dt-binding: document QCOM platforms for CTCU device Jie Gan
2026-02-05 11:50 ` Krzysztof Kozlowski
2026-02-27 8:15 ` Jie Gan
2026-02-04 2:22 ` [PATCH v3 2/3] arm64: dts: qcom: hamoa: enable ETR and CTCU devices Jie Gan
2026-02-17 11:45 ` Abel Vesa
2026-02-04 2:22 ` [PATCH v3 3/3] arm64: dts: qcom: sm8750: " Jie Gan
2026-02-17 11:45 ` Abel Vesa
2026-02-27 10:10 ` [PATCH v3 0/3] Enable CTCU and ETR devices for multiple QCOM platforms Suzuki K Poulose
2026-03-16 1:51 ` Jie Gan
2026-05-11 10:10 ` Jie Gan
2026-05-29 10:26 ` Jie Gan
2026-05-29 11:10 ` Suzuki K Poulose [this message]
2026-07-08 1:39 ` Jie Gan
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=6b7294a1-8c13-42aa-9f64-5b5c9af0b41f@arm.com \
--to=suzuki.poulose@arm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=james.clark@linaro.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-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@linaro.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