From: Jie Gan <quic_jiegan@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
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: Fri, 4 Jul 2025 16:14:35 +0800 [thread overview]
Message-ID: <cbfb9159-1c80-4db4-b5d7-036980a1a44a@quicinc.com> (raw)
In-Reply-To: <9c11bd92-ff2e-493f-8e71-fd8d3f8b32e6@kernel.org>
On 7/4/2025 4:10 PM, Krzysztof Kozlowski wrote:
> On 04/07/2025 10:07, Jie Gan wrote:
>>
>>>
>>>> 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.
>>>
>>> This is explained in writing bindings.
>>
>> Yeah, explained in the code lines..
> I meant explained in writing bindings document. Please read writing
> bindings first.
OK, will check, sorry for the misunderstanding.
Thanks,
Jie
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2025-07-04 8:14 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 ` [PATCH v2 0/2] Enable CTCU device for QCS8300 Jie Gan
2025-07-04 2:41 ` 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 [this message]
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=cbfb9159-1c80-4db4-b5d7-036980a1a44a@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=krzk@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).