From: Jie Gan <quic_jiegan@quicinc.com>
To: Jie Gan <jie.gan@oss.qualcomm.com>,
Suzuki K Poulose <suzuki.poulose@arm.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>,
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 v2 0/2] Enable CTCU device for QCS8300
Date: Wed, 25 Jun 2025 08:59:43 +0800 [thread overview]
Message-ID: <338a9ee1-10aa-4bd2-9b0a-5006ed571bb9@quicinc.com> (raw)
In-Reply-To: <20250624095905.7609-1-jie.gan@oss.qualcomm.com>
On 6/24/2025 5:59 PM, Jie Gan wrote:
> Enable CTCU device for QCS8300 platform. Add a fallback mechnasim in binding to utilize
> the compitable of the SA8775p platform becuase the CTCU for QCS8300 shares same
> configurations as SA8775p platform.
Hi dear maintainers,
I just realized it would be more efficient to introduce a common
compatible string for SoCs that include two TMC ETR devices.
Most of these SoCs share the same CTCU data configuration, such as the
offsets for the ATID and IRQ registers, because they integrate the same
version of the CTCU hardware.
So I propose introducing a common compatible string,
"coresight-ctcu-v2", to simplify the device tree configuration for these
platforms.
Here is the new dt-binding format:
properties:
compatible:
oneOf:
- items:
- enum:
- qcom,sa8775p-ctcu
- qcom,qcs8300-ctcu
- const: qcom,coresight-ctcu-v2
- enum:
- qcom,coresight-ctcu-v2
Thanks,
Jie
>
> Changes in V2:
> 1. Add Krzysztof's R-B tag for dt-binding patch.
> 2. Add Konrad's Acked-by tag for dt patch.
> 3. Rebased on tag next-20250623.
> 4. Missed email addresses for coresight's maintainers in V1, loop them.
> Link to V1 - https://lore.kernel.org/all/20250327024943.3502313-1-jie.gan@oss.qualcomm.com/
>
> Jie Gan (2):
> dt-bindings: arm: add CTCU device for QCS8300
> arm64: dts: qcom: qcs8300: Add CTCU and ETR nodes
>
> .../bindings/arm/qcom,coresight-ctcu.yaml | 9 +-
> arch/arm64/boot/dts/qcom/qcs8300.dtsi | 153 ++++++++++++++++++
> 2 files changed, 160 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2025-06-25 1:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-24 9:59 [PATCH v2 0/2] Enable CTCU device for QCS8300 Jie Gan
2025-06-24 9:59 ` [PATCH v2 1/2] dt-bindings: arm: add " Jie Gan
2025-06-24 9:59 ` [PATCH v2 2/2] arm64: dts: qcom: qcs8300: Add CTCU and ETR nodes Jie Gan
2025-06-25 0:59 ` Jie Gan [this message]
2025-07-04 2:41 ` [PATCH v2 0/2] Enable CTCU device for QCS8300 Jie Gan
2025-07-04 7:54 ` Krzysztof Kozlowski
2025-07-04 8:07 ` Jie Gan
2025-07-04 8:10 ` Krzysztof Kozlowski
2025-07-04 8:14 ` Jie Gan
2025-07-15 0:38 ` Jie Gan
2025-07-15 0:41 ` Jie Gan
2025-07-28 1:08 ` Jie Gan
2025-08-05 4:11 ` Jie Gan
2025-08-05 9:53 ` Mike Leach
2025-08-05 10:25 ` Jie Gan
2025-08-25 1:32 ` 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=338a9ee1-10aa-4bd2-9b0a-5006ed571bb9@quicinc.com \
--to=quic_jiegan@quicinc.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=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=suzuki.poulose@arm.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;
as well as URLs for NNTP newsgroup(s).