The connections between CoreSight sources, links and sinks is not obvious without documentation or access to the device tree / ACPI definitions for the platform.
This patchset provides sysfs links to enable the user to follow the trace patch from source to sink.
Components in the trace path are updated to have a connections sysfs group, which collates all the links for that component.
This supplements the sysfs links created for connections between CTI devices and applies on top of that work from the patchset [1].
Adaptation of an original patchset [2] from Suzuki, reusing 2 patches unchanged with update to 3rd adapt to the CTI v4 RFC set and new code to add default connections group.
Tested on DB410c 5.3-rc1, coresight/next branch.
[1] https://lists.linaro.org/pipermail/coresight/2019-August/003146.html [2] https://lists.linaro.org/pipermail/coresight/2019-May/002803.html
Mike Leach (2): coresight: Move common sysfs functions into separate file. coresight: add default connections group in sysfs to components.
Suzuki K Poulose (3): coresight: Pass coresight_device for coresight_release_platform_data coresight: add return value for fixup connections coresight: Expose device connections via sysfs
drivers/hwtracing/coresight/Makefile | 3 +- drivers/hwtracing/coresight/coresight-etm3x.c | 1 + drivers/hwtracing/coresight/coresight-etm4x.c | 1 + .../hwtracing/coresight/coresight-funnel.c | 1 + .../hwtracing/coresight/coresight-platform.c | 2 +- drivers/hwtracing/coresight/coresight-priv.h | 10 +- .../coresight/coresight-replicator.c | 1 + drivers/hwtracing/coresight/coresight-stm.c | 1 + drivers/hwtracing/coresight/coresight-sysfs.c | 232 ++++++++++++++++++ drivers/hwtracing/coresight/coresight-tmc.c | 1 + drivers/hwtracing/coresight/coresight.c | 146 ++++------- include/linux/coresight.h | 7 + 12 files changed, 306 insertions(+), 100 deletions(-) create mode 100644 drivers/hwtracing/coresight/coresight-sysfs.c