From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Mike Leach <mike.leach@linaro.org>,
Mao Jinlong <quic_jinlmao@quicinc.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, 8 Feb 2023 16:36:40 +0000 [thread overview]
Message-ID: <bb6c9df9-af9b-873e-85bd-a29d00bb39d7@arm.com> (raw)
In-Reply-To: <CAJ9a7ViA5BsbLjRWMsttmpmcPh1yUXK8J79k-pqYybVZkMQHXQ@mail.gmail.com>
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
next prev parent reply other threads:[~2023-02-08 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 11:16 [PATCH] coresight: core: Add sysfs node to reset all sources and sinks Mao Jinlong
2023-02-08 16:16 ` Mike Leach
2023-02-08 16:20 ` Mike Leach
2023-02-08 16:36 ` Suzuki K Poulose [this message]
2023-02-09 3:02 ` Jinlong Mao
2023-02-09 14:56 ` Mike Leach
2023-03-01 15:04 ` Jinlong Mao
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=bb6c9df9-af9b-873e-85bd-a29d00bb39d7@arm.com \
--to=suzuki.poulose@arm.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_jinlmao@quicinc.com \
--cc=quic_taozha@quicinc.com \
--cc=quic_tingweiz@quicinc.com \
--cc=quic_yuanfang@quicinc.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