Hi Suzuki,
On Thu, May 30, 2019 at 05:44:54PM +0100, Suzuki K Poulose wrote:
Coresight device connections are a bit complicated and is not exposed currently to the user. One has to look at the platform descriptions (DT bindings or ACPI bindings) to make an understanding. Given the new naming scheme, it will be helpful to have this information to choose the appropriate devices for tracing. This patch exposes the device connections via links in the sysfs directories.
e.g, for a connection devA[OutputPort_X] -> devB[InputPort_Y] is represented as two symlinks:
/sys/bus/coresight/.../devA/out:X -> /sys/bus/coresight/.../devB /sys/bus/coresight/.../devB/in:Y -> /sys/bus/coresight/.../devA
Applies on coresight/next tree.
This is split from the ACPI bindings series. No functional changes.
I tested this patch set and it works well as expected on my Juno board.
FWIW:
Tested-by: Leo Yan leo.yan@linaro.org
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/coresight-platform.c | 2 +- drivers/hwtracing/coresight/coresight-priv.h | 3 +- drivers/hwtracing/coresight/coresight.c | 148 +++++++++++++++++++---- include/linux/coresight.h | 4 + 4 files changed, 132 insertions(+), 25 deletions(-)
-- 2.7.4