From: Jinlong Mao <quic_jinlmao@quicinc.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>,
Mike Leach <mike.leach@linaro.org>,
James Clark <james.clark@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <coresight@lists.linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v1 0/2] Add Qualcomm extended CTI support
Date: Tue, 17 Dec 2024 15:50:47 +0800 [thread overview]
Message-ID: <f839a280-aa76-4963-9580-a6e089136bb5@quicinc.com> (raw)
In-Reply-To: <742d1cec-13ec-4f08-b7f3-611c6d602b3b@quicinc.com>
On 2024/10/10 17:49, Jinlong Mao wrote:
>
>
> On 2024/9/3 20:18, Mao Jinlong wrote:
>> The QCOM extended CTI is a heavily parameterized version of ARM’s CSCTI.
>> It allows a debugger to send to trigger events to a processor or to send
>> a trigger event to one or more processors when a trigger event occurs on
>> another processor on the same SoC, or even between SoCs.
>>
>> QCOM extended CTI supports up to 128 triggers. And some of the register
>> offsets are changed.
>>
>> The commands to configure CTI triggers are the same as ARM's CTI.
>>
>
> Hi Reviewers,
>
> Could you please help to provide some comments from the design point of
> view for the changes ?
>
> The main difference of extended CTI to the normal CTI is that the
> address mapping is changed and it supports a max of 128 trigger signals.
>
> On one soc, there will be both normal arm CTIs and QCOM extended CTIs.
>
> As max trigger number becomes 128. So triger registers becomes 4.
>
> Like CTITRIGINSTATUS --- > CTITRIGINSTATUS_EXTENDED(n) (0x040 + (4
> * n)) n is 0 to 4.
>
> Thanks
> Jinlong Mao
Gentle reminder for the review from the code design point of view.
>
>> Mao Jinlong (2):
>> dt-bindings: arm: Add Qualcomm extended CTI
>> coresight: cti: Add Qualcomm extended CTI support
>>
>> .../bindings/arm/arm,coresight-cti.yaml | 14 ++
>> .../hwtracing/coresight/coresight-cti-core.c | 75 +++++++----
>> .../coresight/coresight-cti-platform.c | 16 ++-
>> .../hwtracing/coresight/coresight-cti-sysfs.c | 124 ++++++++++++++----
>> drivers/hwtracing/coresight/coresight-cti.h | 123 +++++++++++------
>> 5 files changed, 253 insertions(+), 99 deletions(-)
>>
>
prev parent reply other threads:[~2024-12-17 7:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 12:18 Mao Jinlong
2024-09-03 12:18 ` [PATCH v1 1/2] dt-bindings: arm: Add Qualcomm extended CTI Mao Jinlong
2024-09-03 12:42 ` Krzysztof Kozlowski
2025-04-28 7:31 ` Jinlong Mao
2025-04-28 7:39 ` Krzysztof Kozlowski
2025-04-28 8:09 ` Jinlong Mao
2025-04-28 11:40 ` Jinlong Mao
2024-09-03 12:18 ` [PATCH v1 2/2] coresight: cti: Add Qualcomm extended CTI support Mao Jinlong
2024-09-03 12:44 ` Krzysztof Kozlowski
2024-10-10 9:49 ` [PATCH v1 0/2] " Jinlong Mao
2024-12-17 7:50 ` Jinlong Mao [this message]
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=f839a280-aa76-4963-9580-a6e089136bb5@quicinc.com \
--to=quic_jinlmao@quicinc.com \
--cc=agross@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=james.clark@arm.com \
--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+dt@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
all inboxes | Powered by JetHome®