From: Leo Yan <leo.yan@linaro.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: coresight@lists.linaro.org, mathieu.poirier@linaro.org,
linux-arm-kernel@lists.infradead.org, mike.leach@linaro.org
Subject: Re: [PATCH 0/3] coresight: Expose device connections via sysfs
Date: Mon, 3 Jun 2019 16:45:50 +0800 [thread overview]
Message-ID: <20190603084550.GA29174@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <1559234697-15743-1-git-send-email-suzuki.poulose@arm.com>
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
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-06-03 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 16:44 [PATCH 0/3] coresight: Expose device connections via sysfs Suzuki K Poulose
2019-05-30 16:44 ` [PATCH 1/3] coresight: Pass coresight_device for coresight_release_platform_data Suzuki K Poulose
2019-05-30 16:44 ` [PATCH 2/3] coresight: add return value for fixup connections Suzuki K Poulose
2019-05-30 16:44 ` [PATCH 3/3] coresight: Expose device connections via sysfs Suzuki K Poulose
2019-06-03 8:45 ` Leo Yan [this message]
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=20190603084550.GA29174@leoy-ThinkPad-X240s \
--to=leo.yan@linaro.org \
--cc=coresight@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.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