On 08/09/2025 03:01, 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 1accd7cbd54b..042c4fa39e55 100644 --- a/drivers/hwtracing/coresight/coresight-core.c +++ b/drivers/hwtracing/coresight/coresight-core.c @@ -580,6 +580,30 @@ struct coresight_device *coresight_get_sink(struct coresight_path *path) } EXPORT_SYMBOL_GPL(coresight_get_sink); +/**
- coresight_get_in_port_dest: get the in-port number of the dest device
- that is connected to the src device.
- @src: csdev of the source device.
- @dest: csdev of the destination device.
- Return: port number upon success or -EINVAL for fail.
- */
+int coresight_get_in_port_dest(struct coresight_device *src,
Please could we make this more explicit :
/* * Find the input port number at @csdev where a @remote * device is connected to. */ coresight_get_in_port(struct coresight_device *csdev, struct coresight_device *remote) {
} Suzuki