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 #
31 channels. When an input trigger becomes active, the attached channel will
32 become active. Any output trigger attached to that channel will also
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
51 (e.g. UART), or be propagated off chip as hardware IO lines.
60 ---------------------------
78 *Key file items are:-*
82    * ``ctmid`` : associated CTM - only relevant if system has multiple CTI+CTM
84    * ``nr_trigger_cons`` : total connections - triggers<N> directories.
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.
166    * ``chan_set``: Set the channel - the set state will be propagated around
176    * ``chan_inuse``: Show the current channels attached to any signal
177    * ``chan_free``: Show channels with no attached signals.
180    * ``chan_xtrigs_in``: Read to show the input triggers attached to
182    * ``chan_xtrigs_out``:Read to show the output triggers attached to
208    0-1,3