diff options
author | Alexander Shishkin <alexander.shishkin@linux.intel.com> | 2016-09-19 17:06:25 +0200 |
---|---|---|
committer | Alexander Shishkin <alexander.shishkin@linux.intel.com> | 2016-11-18 16:11:35 +0100 |
commit | ee01aebbe2c4c196142bdb8074812dfe44830725 (patch) | |
tree | 23f95b2c417392f426f38b85e2b7bd2131356edd /Documentation/trace | |
parent | intel_th: gth: Handle host mode correctly (diff) | |
download | linux-ee01aebbe2c4c196142bdb8074812dfe44830725.tar.xz linux-ee01aebbe2c4c196142bdb8074812dfe44830725.zip |
intel_th: Document debug host mode
Signed-off-by: Alexander Shishkin <alexander.shishkin@linux.intel.com>
Diffstat (limited to 'Documentation/trace')
-rw-r--r-- | Documentation/trace/intel_th.txt | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/Documentation/trace/intel_th.txt b/Documentation/trace/intel_th.txt index f7fc5ba5df8d..f92070e7dde0 100644 --- a/Documentation/trace/intel_th.txt +++ b/Documentation/trace/intel_th.txt @@ -97,3 +97,25 @@ $ echo 0 > /sys/bus/intel_th/devices/0-msc0/active # and now you can collect the trace from the device node: $ cat /dev/intel_th0/msc0 > my_stp_trace + +Host Debugger Mode +================== + +It is possible to configure the Trace Hub and control its trace +capture from a remote debug host, which should be connected via one of +the hardware debugging interfaces, which will then be used to both +control Intel Trace Hub and transfer its trace data to the debug host. + +The driver needs to be told that such an arrangement is taking place +so that it does not touch any capture/port configuration and avoids +conflicting with the debug host's configuration accesses. The only +activity that the driver will perform in this mode is collecting +software traces to the Software Trace Hub (an stm class device). The +user is still responsible for setting up adequate master/channel +mappings that the decoder on the receiving end would recognize. + +In order to enable the host mode, set the 'host_mode' parameter of the +'intel_th' kernel module to 'y'. None of the virtual output devices +will show up on the intel_th bus. Also, trace configuration and +capture controlling attribute groups of the 'gth' device will not be +exposed. The 'sth' device will operate as usual. |