mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jinlong Mao <quic_jinlmao@quicinc.com>
To: Mike Leach <mike.leach@linaro.org>,
	Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
	Leo Yan <leo.yan@linaro.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	<coresight@lists.linaro.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
	Tingwei Zhang <quic_tingweiz@quicinc.com>,
	Yuanfang Zhang <quic_yuanfang@quicinc.com>,
	Tao Zhang <quic_taozha@quicinc.com>,
	Hao Zhang <quic_hazha@quicinc.com>
Subject: Re: [PATCH] coresight: core: Add sysfs node to reset all sources and sinks
Date: Wed, 1 Mar 2023 23:04:14 +0800	[thread overview]
Message-ID: <0308d380-bc8b-cb66-55cd-b0934d8f9676@quicinc.com> (raw)
In-Reply-To: <CAJ9a7Vh08A8b7YLF=pYPudB0CZ0XjEpF=4YHrNNd7xo_JQGYaA@mail.gmail.com>

Hi Mike & Suzuki,

On 2/9/2023 10:56 PM, Mike Leach wrote:
> Hi,
>
> On Thu, 9 Feb 2023 at 03:02, Jinlong Mao <quic_jinlmao@quicinc.com> wrote:
>>
>> On 2/9/2023 12:36 AM, Suzuki K Poulose wrote:
>>> On 08/02/2023 16:20, Mike Leach wrote:
>>>> Quick correction - you need to look for enable_source  / enable_sink
>>>> files and disable those that are currently '1'
>>>>
>>>> Mike
>>>>
>>>> On Wed, 8 Feb 2023 at 16:16, Mike Leach <mike.leach@linaro.org> wrote:
>>>>> Hi
>>>>>
>>>>> As this is a sysfs only update - would it not be easier to simply use
>>>>> a shell script to iterate through coresight/devices/ looking for
>>>>> disable_source / disable_sink files and setting those accordingly?
>>>>>
>>>>> See tools/perf/tests/shell/test_arm_coresight.sh for an example of a
>>>>> script that does similar iteration to test coresight in perf
>>>>>
>>> +1
>>>
>>> Suzuki
>> Hi Mike & Suzuki,
>>
>> Sometimes user just want to have some quick test from PC with adb commands.
>> It is very easy to reset all sources and sinks' status by command below.
>> echo 1 > /sys/bus/coresight/reset_source_sink
>>
> Users of coresight via sysfs will have to know how to use the
> coresight infrastructure in order to enable the sources and sinks in
> the first place -
> e.g
> echo 1 > /sys/bus/coresight/devices/tmc_etr0/enable_sink
> echo 1 > /sys/bus/coresight/devices/etm0/enable_source
>
> Given that they are aware of which sources and sinks they enabled -
> disabling them should be simple.
>
>
>> Preparing the script for test is not easy for users who are not familiar
>> with the coresight framework.
>>
> If there is a genuine use case were a user has opened so many sources
> on the command line that they need a simpler way of closing them than
> repeating the enabled commands with an
> echo 0 > ...
> then any script could be shipped as part of kernel/tools/coresight or
> kernel/samples/coresight - they would not have to write it themselves,
> and just run it from the command line - for example :-
> ./kernel/tools/coresight/scripts/sysfs_disable_sources_and_sinks.sh
>
> Realistically users will only try out a couple of devices as the
> usefulness of the sysfs interface is really limited to testing or
> board bring up.
> Any complex use with sysfs - as in the coresight tests I mentioned
> earlier is really going to be done by scripting.
>
>
> Regards
>
> Mike

There is also requirement that reset all the sources and sinks in an 
user space daemon.
For such requirement, I think it is better to use only once sysfs node 
instead of iterating through coresight/device folder in an user space 
daemon.

Thanks
Jinlong Mao

>> Thanks
>> Jinlong Mao
>>
>>>
>
>

  reply	other threads:[~2023-03-01 15:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 11:16 Mao Jinlong
2023-02-08 16:16 ` Mike Leach
2023-02-08 16:20   ` Mike Leach
2023-02-08 16:36     ` Suzuki K Poulose
2023-02-09  3:02       ` Jinlong Mao
2023-02-09 14:56         ` Mike Leach
2023-03-01 15:04           ` Jinlong Mao [this message]
2023-03-17  6:18             ` Jinlong Mao
2023-03-17  9:10               ` Suzuki K Poulose

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=0308d380-bc8b-cb66-55cd-b0934d8f9676@quicinc.com \
    --to=quic_jinlmao@quicinc.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=coresight@lists.linaro.org \
    --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=quic_hazha@quicinc.com \
    --cc=quic_taozha@quicinc.com \
    --cc=quic_tingweiz@quicinc.com \
    --cc=quic_yuanfang@quicinc.com \
    --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

all inboxes | Powered by JetHome®