From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Jie Gan <jie.gan@oss.qualcomm.com>,
Mike Leach <mike.leach@linaro.org>,
James Clark <james.clark@linaro.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Tingwei Zhang <tingwei.zhang@oss.qualcomm.com>,
Mao Jinlong <jinlong.mao@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-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v10 1/8] coresight: core: Refactoring ctcu_get_active_port and make it generic
Date: Thu, 22 Jan 2026 10:00:02 +0000 [thread overview]
Message-ID: <525fe4ad-3d3e-4c05-a6f5-da91157f362e@arm.com> (raw)
In-Reply-To: <20260122-enable-byte-cntr-for-ctcu-v10-1-22978e3c169f@oss.qualcomm.com>
On 22/01/2026 02:08, Jie Gan wrote:
> Remove ctcu_get_active_port from CTCU module and add it to the core
> framework.
>
> The port number is crucial for the CTCU device to identify which ETR
> it serves. With the port number we can correctly get required parameters
> of the CTCU device in TMC module.
>
> Reviewed-by: Mike Leach <mike.leach@linaro.org>
> Signed-off-by: Jie Gan <jie.gan@oss.qualcomm.com>
> ---
> drivers/hwtracing/coresight/coresight-core.c | 24 +++++++++++++++++++++++
> drivers/hwtracing/coresight/coresight-ctcu-core.c | 19 +-----------------
> drivers/hwtracing/coresight/coresight-priv.h | 2 ++
> 3 files changed, 27 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/hwtracing/coresight/coresight-core.c b/drivers/hwtracing/coresight/coresight-core.c
> index c660cf8adb1c..0e8448784c62 100644
> --- a/drivers/hwtracing/coresight/coresight-core.c
> +++ b/drivers/hwtracing/coresight/coresight-core.c
> @@ -585,6 +585,30 @@ struct coresight_device *coresight_get_sink(struct coresight_path *path)
> }
> EXPORT_SYMBOL_GPL(coresight_get_sink);
>
> +/**
> + * coresight_get_in_port: Find the input port number at @csdev where a @remote
> + * device is connected to.
This doesn't match the code ?
We are looking at the remote devices' in_connections ?
> + *
> + * @csdev: csdev of the device.
> + * @remote: csdev of the remote device which is connected to @csdev.
> + *
> + * Return: port number upon success or -EINVAL for fail.
> + */
> +int coresight_get_in_port(struct coresight_device *csdev,
> + struct coresight_device *remote)
> +{
> + struct coresight_platform_data *pdata = remote->pdata;
> + int i;
> +
> + for (i = 0; i < pdata->nr_inconns; ++i) {
> + if (pdata->in_conns[i]->src_dev == csdev)
> + return pdata->in_conns[i]->dest_port;
> + }
Suzuki
next prev parent reply other threads:[~2026-01-22 10:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 2:08 [PATCH v10 0/8] coresight: ctcu: Enable byte-cntr function for TMC ETR Jie Gan
2026-01-22 2:08 ` [PATCH v10 1/8] coresight: core: Refactoring ctcu_get_active_port and make it generic Jie Gan
2026-01-22 10:00 ` Suzuki K Poulose [this message]
2026-01-23 1:27 ` Jie Gan
2026-01-22 2:08 ` [PATCH v10 2/8] coresight: tmc: add create/clean functions for etr_buf_list Jie Gan
2026-01-22 2:08 ` [PATCH v10 3/8] coresight: tmc: Introduce sysfs_read_ops to wrap sysfs read operations Jie Gan
2026-01-22 10:07 ` Suzuki K Poulose
2026-01-23 1:32 ` Jie Gan
2026-01-22 2:08 ` [PATCH v10 4/8] coresight: etr: refactor the tmc_etr_get_catu_device function Jie Gan
2026-01-26 16:10 ` Suzuki K Poulose
2026-01-27 1:00 ` Jie Gan
2026-01-22 2:08 ` [PATCH v10 5/8] dt-bindings: arm: add an interrupt property for Coresight CTCU Jie Gan
2026-01-26 17:22 ` Suzuki K Poulose
2026-01-27 0:59 ` Jie Gan
2026-01-22 2:08 ` [PATCH v10 6/8] coresight: ctcu: enable byte-cntr for TMC ETR devices Jie Gan
2026-01-22 2:08 ` [PATCH v10 7/8] coresight: tmc: integrate byte-cntr's read_ops with sysfs file_ops Jie Gan
2026-01-22 2:08 ` [PATCH v10 8/8] arm64: dts: qcom: lemans: add interrupts to CTCU device 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=525fe4ad-3d3e-4c05-a6f5-da91157f362e@arm.com \
--to=suzuki.poulose@arm.com \
--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@linaro.org \
--cc=jie.gan@oss.qualcomm.com \
--cc=jinlong.mao@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®