bindings/arm/arm%2Ccoresight-cti.yaml

5 $id: http://devicetree.org/schemas/arm/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
17   The CTI component properties define the connections between the individual
18   CTI and the components it is directly connected to, consisting of input and
20   output hardware trigger signals (8 each for v1 CTI, 32 each for v2 CTI). The
30   In general the connections between CTI and components via the trigger signals
31   are implementation defined, except when the CTI is connected to an ARM v8
35   between CTI and the CPU core and ETM if present. In the case of a v8
36   architecturally connected CTI an additional compatible string is used to
37   indicate this feature (arm,coresight-cti-v8-arch).
39   When CTI trigger connection information is unavailable then a minimal driver
44   on the connections between the CTI and other components for correct operation.
48   between CTI and other CoreSight components.
50   Certain triggers between CoreSight devices and the CTI have specific types
52   constants defined in <dt-bindings/arm/coresight-cti-dt.h>
54   For example a CTI connected to a core will usually have a DBGREQ signal. This
74           - arm,coresight-cti
80     pattern: "^cti(@[0-9a-f]+)$"
84           - const: arm,coresight-cti
87           - const: arm,coresight-cti-v8-arch
88           - const: arm,coresight-cti
96       Handle to cpu this CTI is associated with.
101   arm,cti-ctm-id:
104       Defines the CTM this CTI is connected to, in large systems with multiple
105       separate CTI/CTM nets. Typically multi-socket systems where the CTM is
112       When the associated trace device is enabled, then the respective CTI
113       will be enabled. Use in CTI base node when compatible string
114       arm,coresight-cti-v8-arch used. If the associated device has not been
134       between this CTI and another hardware device. This device may be a CPU,
151           When the associated trace device is enabled, then the respective CTI
163           List of CTI trigger in signal numbers in use by a trig-conns node.
170           List of constants representing the types for the CTI trigger in
180           List of CTI trigger out signal numbers in use by a trig-conns node.
187           List of constants representing the types for the CTI trigger out
197           List of CTI trigger out signals that will be blocked from becoming
205           Principle use for CTI that are connected to non-CoreSight devices, or
233         const: arm,coresight-cti-v8-arch
242   # minimum CTI definition. DEVID register used to set number of triggers.
244     cti@20020000 {
245       compatible = "arm,coresight-cti", "arm,primecell";
251   #  v8 architecturally defined CTI - CPU + ETM connections generated by the
254     cti@859000 {
255       compatible = "arm,coresight-cti-v8-arch", "arm,coresight-cti",
265   # Implementation defined CTI - CPU + ETM connections explicitly defined..
266   # Shows use of type constants from dt-bindings/arm/coresight-cti-dt.h
269     #include <dt-bindings/arm/coresight-cti-dt.h>
271     cti@858000 {
272       compatible = "arm,coresight-cti", "arm,primecell";
278       arm,cti-ctm-id = <1>;
312   # Implementation defined CTI - non CoreSight component connections.
314     cti@20110000 {
315       compatible = "arm,coresight-cti", "arm,primecell";