From: Jie Gan <quic_jiegan@quicinc.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>
Cc: Tingwei Zhang <quic_tingweiz@quicinc.com>,
Jinlong Mao <quic_jinlmao@quicinc.com>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 0/2] Enable CTCU device for QCS8300
Date: Wed, 14 May 2025 16:00:12 +0800 [thread overview]
Message-ID: <d87a6bba-eaed-4ac4-a272-3bb38b1607dc@quicinc.com> (raw)
In-Reply-To: <20250327024943.3502313-1-jie.gan@oss.qualcomm.com>
On 3/27/2025 10:49 AM, 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.
>
Gentle ping for the series.
dt-binding patch has been reviewed by Krzysztof.
dts patch has been acked by Konrad.
Thanks,
Jie
> 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-05-14 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-27 2:49 [PATCH v1 0/2] Enable CTCU device for QCS8300 Jie Gan
2025-03-27 2:49 ` [PATCH v1 1/2] dt-bindings: arm: add " Jie Gan
2025-03-28 8:21 ` Krzysztof Kozlowski
2025-03-27 2:49 ` [PATCH v1 2/2] arm64: dts: qcom: qcs8300: Add CTCU and ETR nodes Jie Gan
2025-04-01 16:37 ` Konrad Dybcio
2025-05-14 8:00 ` Jie Gan [this message]
2025-06-18 2:50 ` [PATCH v1 0/2] Enable CTCU device for QCS8300 Bjorn Andersson
2025-06-18 2:55 ` 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=d87a6bba-eaed-4ac4-a272-3bb38b1607dc@quicinc.com \
--to=quic_jiegan@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_jinlmao@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=robh@kernel.org \
/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