[PATCH v2 0/2] coresight: core: Add device name support

From: Mao Jinlong
Date: Mon Jan 15 2024 - 11:43:38 EST


With current design, the name of the non-cpu bounded coresight
component is the device type with the number. And with 'ls' command
we can get the register address of the component. But from these
information, we can't know what the HW or system the component belongs
to. Add device-name in DT to support it.

cti_sys0 -> ../../../devices/platform/soc@0/138f0000.cti/cti_sys0
cti_sys1 -> ../../../devices/platform/soc@0/13900000.cti/cti_sys1
tpdm0 -> ../../../devices/platform/soc@0/10b0d000.tpdm/tpdm0
tpdm1 -> ../../../devices/platform/soc@0/10c28000.tpdm/tpdm1
tpdm2 -> ../../../devices/platform/soc@0/10c29000.tpdm/tpdm2

Change since V1:
1. Change coresight-name to device name.
2. Add the device-name in coresight dt bindings.

Mao Jinlong (2):
coresight: core: Add device name support
dt-bindings: arm: Add device-name in the coresight components

.../bindings/arm/arm,coresight-catu.yaml | 5 +++
.../bindings/arm/arm,coresight-cpu-debug.yaml | 5 +++
.../bindings/arm/arm,coresight-cti.yaml | 5 +++
.../arm/arm,coresight-dummy-sink.yaml | 5 +++
.../arm/arm,coresight-dummy-source.yaml | 5 +++
.../arm/arm,coresight-dynamic-funnel.yaml | 5 +++
.../arm/arm,coresight-dynamic-replicator.yaml | 5 +++
.../bindings/arm/arm,coresight-etb10.yaml | 5 +++
.../bindings/arm/arm,coresight-etm.yaml | 5 +++
.../arm/arm,coresight-static-funnel.yaml | 5 +++
.../arm/arm,coresight-static-replicator.yaml | 5 +++
.../bindings/arm/arm,coresight-stm.yaml | 5 +++
.../bindings/arm/arm,coresight-tmc.yaml | 5 +++
.../bindings/arm/arm,coresight-tpiu.yaml | 5 +++
.../bindings/arm/qcom,coresight-tpda.yaml | 5 +++
.../bindings/arm/qcom,coresight-tpdm.yaml | 5 +++
drivers/hwtracing/coresight/coresight-core.c | 33 ++++++++++---------
.../hwtracing/coresight/coresight-platform.c | 31 +++++++++++++++++
include/linux/coresight.h | 1 +
19 files changed, 130 insertions(+), 15 deletions(-)

--
2.41.0