From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Jie Gan <jie.gan@oss.qualcomm.com>,
Konrad Dybcio <konrad.dybcio@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
Subject: Re: [PATCH 1/3] dt-binding: document QCOM platforms for CTCU device
Date: Tue, 3 Feb 2026 09:31:55 +0000 [thread overview]
Message-ID: <5911fe77-fe2c-4321-96a9-a1b6b3b5d1e3@arm.com> (raw)
In-Reply-To: <6c823646-9085-409e-a692-ae3e77347742@oss.qualcomm.com>
On 03/02/2026 09:00, Jie Gan wrote:
>
>
> On 2/3/2026 4:50 PM, Konrad Dybcio wrote:
>> On 2/3/26 9:08 AM, Jie Gan wrote:
>>> Document the platforms that fallback to using the qcom,sa8775p-ctcu
>>> compatible for probing.
>>>
>>> Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>
>>> ---
>>> Documentation/devicetree/bindings/arm/qcom,coresight-ctcu.yaml | 4
>>> ++++
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/arm/qcom,coresight-
>>> ctcu.yaml b/Documentation/devicetree/bindings/arm/qcom,coresight-
>>> ctcu.yaml
>>> index e002f87361ad..68853db52bef 100644
>>> --- a/Documentation/devicetree/bindings/arm/qcom,coresight-ctcu.yaml
>>> +++ b/Documentation/devicetree/bindings/arm/qcom,coresight-ctcu.yaml
>>> @@ -29,6 +29,10 @@ properties:
>>> oneOf:
>>> - items:
>>> - enum:
>>> + - qcom,glymur-ctcu
>>> + - qcom,hamoa-ctcu
>>> + - qcom,kaanapali-ctcu
>>> + - qcom,pakala-ctcu
>>
>> Platforms with existing numeric compatibles should continue to use them,
>> so that the mess is somewhat containable
>
> Sure Konrad. So for Pakala, I will change it back to qcom,sm8750-ctcu
Why do we need different compatibles for the others ? Are they not all
compliant to the CTCU programming model ? i.e., sa8775p-ctcu ? or even,
a generic,
qcom,coresight-ctcu
Suzuki
>
> Thanks,
> Jie
>
>>
>> Konrad
>
next prev parent reply other threads:[~2026-02-03 9:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 8:08 [PATCH 0/3] Enable CTCU and ETR devices for multiple QCOM platforms Jie Gan
2026-02-03 8:08 ` [PATCH 1/3] dt-binding: document QCOM platforms for CTCU device Jie Gan
2026-02-03 8:50 ` Konrad Dybcio
2026-02-03 9:00 ` Jie Gan
2026-02-03 9:31 ` Suzuki K Poulose [this message]
2026-02-03 9:36 ` Konrad Dybcio
2026-02-03 9:44 ` Suzuki K Poulose
2026-02-03 10:13 ` Konrad Dybcio
2026-02-03 9:41 ` Jie Gan
2026-02-03 8:08 ` [PATCH 2/3] arm64: dts: qcom: hamoa: enable ETR and CTCU devices Jie Gan
2026-02-03 8:08 ` [PATCH 3/3] arm64: dts: qcom: pakala: " Jie Gan
2026-02-03 8:56 ` Konrad Dybcio
2026-02-03 9:01 ` 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=5911fe77-fe2c-4321-96a9-a1b6b3b5d1e3@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
all inboxes | Powered by JetHome®