trace/coresight/coresight-ect.rst

1 .. SPDX-License-Identifier: GPL-2.0
11 --------------------
21  0 C   0----------->:     :             +======>(other CTI channel IO)
22  0  P  0<-----------:     :             v
24  0000000            : CTI :<=========>*CTM*<====>: CTI :---+
25  #######  in_trigs  :     : (id 0-3)  *****      :::::::   v
26  # ETM #----------->:     :                         ^   #######
27  #     #<-----------:     :                         +---# ETR #
41 CoreSight devices on the trace data path. When these devices are enabled the
42 attached CTIs will also be enabled. By default/on power up the CTIs have
50 The hardware trigger signals can also be connected to non-CoreSight devices
53 All the CTI devices are associated with a CTM. On many systems there will be a
56 a CTM to each other. On these systems a CTM index is declared to associate
60 ---------------------------
62 The CTI devices appear on the existing CoreSight bus alongside the other
75   channels  ctmid  enable  nr_trigger_cons mgmt  power powered  regs
78 *Key file items are:-*
80      If this shows as enabled (1), but ``powered`` shows unpowered (0), then
81      the enable indicates a request to enabled when the device is powered.
82    * ``ctmid`` : associated CTM - only relevant if system has multiple CTI+CTM
84    * ``nr_trigger_cons`` : total connections - triggers<N> directories.
85    * ``powered`` : Read to determine if the CTI is currently powered.
87 *Sub-directories:-*
89    * ``channels``: Contains the channel API - CTI main programming interface.
101 CoreSight and non-CoreSight connections.
119     0-2
123     0-1
135 'regs' sub-directory elements directly.
159 set state on cti_sys0.trigout(1)
166    * ``chan_set``: Set the channel - the set state will be propagated around
173      to list the currently enabled channels on the gate.
199 channel control to activate channel 2. We see the active channel on the
200 ``choutstatus`` register and the active signal on the ``trigoutstatus``
208    0-1,3