From: zhang.chunyan@linaro.org (Chunyan Zhang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V4 2/4] Documentations: Add explanations of the case for non-configurable masters
Date: Tue, 1 Mar 2016 14:35:07 +0800 [thread overview]
Message-ID: <1456814109-21311-3-git-send-email-zhang.chunyan@linaro.org> (raw)
In-Reply-To: <1456814109-21311-1-git-send-email-zhang.chunyan@linaro.org>
For some STM hardware (e.g. ARM CoreSight STM), the masterID associated
to a source is set at the hardware level and not user configurable.
Since the masterID information isn't available to SW, introducing
a new value of -1 to reflect this reality.
Signed-off-by: Chunyan Zhang <zhang.chunyan@linaro.org>
---
Documentation/trace/stm.txt | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/trace/stm.txt b/Documentation/trace/stm.txt
index ea035f9..f03bc2b 100644
--- a/Documentation/trace/stm.txt
+++ b/Documentation/trace/stm.txt
@@ -47,6 +47,12 @@ through 127 in it. Now, any producer (trace source) identifying itself
with "user" identification string will be allocated a master and
channel from within these ranges.
+$ cat /config/stp-policy/dummy_stm.my-policy/user/masters
+-1 -1
+
+Would indicate the masters for this rule are set in hardware and
+not configurable in user space.
+
These rules can be nested, for example, one can define a rule "dummy"
under "user" directory from the example above and this new rule will
be used for trace sources with the id string of "user/dummy".
--
1.9.1
next prev parent reply other threads:[~2016-03-01 6:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 6:35 [PATCH V4 0/4] Introduce CoreSight STM support Chunyan Zhang
2016-03-01 6:35 ` [PATCH V4 1/4] stm class: provision for statically assigned masterIDs Chunyan Zhang
2016-03-01 6:35 ` Chunyan Zhang [this message]
2016-03-01 6:35 ` [PATCH V4 3/4] coresight-stm: Bindings for System Trace Macrocell Chunyan Zhang
2016-03-01 6:35 ` [PATCH V4 4/4] coresight-stm: adding driver for CoreSight STM component Chunyan Zhang
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=1456814109-21311-3-git-send-email-zhang.chunyan@linaro.org \
--to=zhang.chunyan@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).