From: Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: mathieu.poirier@linaro.org, alexander.shishkin@linux.intel.com,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
swboyd@chromium.org, leo.yan@linaro.org,
linux-arm-kernel@lists.infradead.org, mike.leach@linaro.org
Subject: Re: [RFC PATCH] coresight: dynamic-replicator: Fix handling of multiple connections
Date: Tue, 07 Apr 2020 16:59:05 +0530 [thread overview]
Message-ID: <39a2b3fff165a108fa59d72b630b5f14@codeaurora.org> (raw)
In-Reply-To: <906d374d-a4d6-f2f2-6845-88b97a5ff7d9@arm.com>
Hi Suzuki,
Thanks for looking into this issue.
On 2020-04-07 15:54, Suzuki K Poulose wrote:
> On 04/07/2020 10:46 AM, Sai Prakash Ranjan wrote:
>
> There seems to be two replicators back to back here. What is connected
> to the other output of both of them ? Are there any TPIUs ? What
> happens
> if you choose a sink on the other end of "swao_replicator" (ETB ?)
>
The other outport of swao replicator is connected to EUD which is a
QCOM specific HW which can be used as a sink like USB.
And the other outport of other replicator(replicator_out) is connected
to
TPIU.
> After boot, what do the idfilter registers read for both the
> replicators ?
>
Added some prints in replicator_probe.
replicator probe ret=-517 devname=6046000.replicator idfilter0=0x0
idfilter1=0x0
replicator probe ret=0 devname=6b06000.replicator idfilter0=0xff
idfilter1=0xff
replicator probe ret=0 devname=6046000.replicator idfilter0=0xff
idfilter1=0xff
>
> I believe we need to properly assign the TRACE_IDs for tracing
> sessions,
> (rather than static ids) in a way such that we could filter them and
> use
> the multiple sinks in parallel for separate trace sessions and this is
> not simple (involves kernel driver changes and the perf tool to be able
> to decode the trace id changes too).
>
>
> So for the moment, we need to :
>
> 1) Disallow turning the replicator ON, when it is already turned ON
> 2) Do what your patch does. i.e, disable the other end while one end
> is turned on.
>
> Thoughts ?
>
Sounds good to me, Mike would have some comments.
Thanks,
Sai
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
member
of Code Aurora Forum, hosted by The Linux Foundation
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-04-07 11:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 10:28 [RFC PATCH] coresight: dynamic-replicator: Fix handling of multiple connections Sai Prakash Ranjan
2020-04-06 10:55 ` Mike Leach
2020-04-07 9:46 ` Sai Prakash Ranjan
2020-04-07 10:24 ` Suzuki K Poulose
2020-04-07 11:29 ` Sai Prakash Ranjan [this message]
2020-04-07 13:08 ` Suzuki K Poulose
2020-04-07 13:56 ` Sai Prakash Ranjan
2020-04-07 14:53 ` Suzuki K Poulose
2020-04-07 15:18 ` Sai Prakash Ranjan
2020-04-08 22:43 ` Suzuki K Poulose
2020-04-09 7:16 ` Stephen Boyd
2020-04-09 7:51 ` Sai Prakash Ranjan
2020-04-09 9:17 ` Suzuki K Poulose
2020-04-09 9:34 ` Sai Prakash Ranjan
2020-04-23 12:21 ` Sai Prakash Ranjan
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=39a2b3fff165a108fa59d72b630b5f14@codeaurora.org \
--to=saiprakash.ranjan@codeaurora.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=leo.yan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.com \
--cc=swboyd@chromium.org \
/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;
as well as URLs for NNTP newsgroup(s).