Lines Matching full:cti

5 $id: http://devicetree.org/schemas/arm/coresight-cti.yaml#
8 title: ARM Coresight Cross Trigger Interface (CTI) device.
11   The CoreSight Embedded Cross Trigger (ECT) consists of CTI devices connected
18   The CTI component properties define the connections between the individual
19   CTI and the components it is directly connected to, consisting of input and
21   output hardware trigger signals (8 each for v1 CTI, 32 each for v2 CTI). The
31   In general the connections between CTI and components via the trigger signals
32   are implementation defined, except when the CTI is connected to an ARM v8
36   between CTI and the CPU core and ETM if present. In the case of a v8
37   architecturally connected CTI an additional compatible string is used to
38   indicate this feature (arm,coresight-cti-v8-arch).
40   When CTI trigger connection information is unavailable then a minimal driver
45   on the connections between the CTI and other components for correct operation.
49   between CTI and other CoreSight components.
51   Certain triggers between CoreSight devices and the CTI have specific types
53   constants defined in <dt-bindings/arm/coresight-cti-dt.h>
55   For example a CTI connected to a core will usually have a DBGREQ signal. This
75           - arm,coresight-cti
81     pattern: "^cti(@[0-9a-f]+)$"
85           - const: arm,coresight-cti
88           - const: arm,coresight-cti-v8-arch
89           - const: arm,coresight-cti
99       base cti node if compatible string arm,coresight-cti-v8-arch is used,
102   arm,cti-ctm-id:
105       Defines the CTM this CTI is connected to, in large systems with multiple
106       separate CTI/CTM nets. Typically multi-socket systems where the CTM is
113       When the associated trace device is enabled, then the respective CTI
114       will be enabled. Use in a trig-conns node, or in CTI base node when
115       compatible string arm,coresight-cti-v8-arch used. If the associated
133       between this CTI and another hardware device. This device may be a CPU,
147           List of CTI trigger in signal numbers in use by a trig-conns node.
154           List of constants representing the types for the CTI trigger in
164           List of CTI trigger out signal numbers in use by a trig-conns node.
171           List of constants representing the types for the CTI trigger out
181           List of CTI trigger out signals that will be blocked from becoming
189           Principle use for CTI that are connected to non-CoreSight devices, or
217         const: arm,coresight-cti-v8-arch
226   # minimum CTI definition. DEVID register used to set number of triggers.
228     cti@20020000 {
229       compatible = "arm,coresight-cti", "arm,primecell";
235   #  v8 architecturally defined CTI - CPU + ETM connections generated by the
238     cti@859000 {
239       compatible = "arm,coresight-cti-v8-arch", "arm,coresight-cti",
249   # Implementation defined CTI - CPU + ETM connections explicitly defined..
250   # Shows use of type constants from dt-bindings/arm/coresight-cti-dt.h
253     #include <dt-bindings/arm/coresight-cti-dt.h>
255     cti@858000 {
256       compatible = "arm,coresight-cti", "arm,primecell";
262       arm,cti-ctm-id = <1>;
296   # Implementation defined CTI - non CoreSight component connections.
298     cti@20110000 {
299       compatible = "arm,coresight-cti", "arm,primecell";