From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752480AbcBFLGd (ORCPT ); Sat, 6 Feb 2016 06:06:33 -0500 Received: from mail-pa0-f48.google.com ([209.85.220.48]:32993 "EHLO mail-pa0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752421AbcBFLG3 (ORCPT ); Sat, 6 Feb 2016 06:06:29 -0500 From: Chunyan Zhang To: mathieu.poirier@linaro.org, alexander.shishkin@linux.intel.com Cc: mike.leach@arm.com, Michael.Williams@arm.com, al.grant@arm.com, tor@ti.com, nicolas.guion@st.com, broonie@kernel.org, robh@kernel.org, pratikp@codeaurora.org, corbet@lwn.net, mark.rutland@arm.com, zhang.lyra@gmail.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-api@vger.kernel.org, linux-doc@vger.kernel.org Subject: [PATCH V3 4/6] Documentations: Add explanations of the case for non-configurable masters Date: Sat, 6 Feb 2016 19:04:30 +0800 Message-Id: <1454756672-12790-5-git-send-email-zhang.chunyan@linaro.org> X-Mailer: git-send-email 1.9.1 In-Reply-To: <1454756672-12790-1-git-send-email-zhang.chunyan@linaro.org> References: <1454756672-12790-1-git-send-email-zhang.chunyan@linaro.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.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 --- 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