Home
last modified time | relevance | path

Searched full:ctis (Results 1 – 4 of 4) sorted by relevance

/linux/Documentation/trace/coresight/
H A Dcoresight-ect.rst33 become active. The active channel is propagated to other CTIs via the CTM,
40 The CTIs are registered by the system to be associated with CPUs and/or other
42 attached CTIs will also be enabled. By default/on power up the CTIs have
46 The hardware trigger connections between CTIs and devices is implementation
55 possible that systems can have nets of CTIs+CTM that are not interconnected by
69 The ``cti_cpu<N>`` named CTIs are associated with a CPU, and any ETM used by
70 that core. The ``cti_sys<N>`` CTIs are general system infrastructure CTIs that
/linux/drivers/hwtracing/coresight/
H A Dcoresight-cti-core.c27 * hardware. We have a list of all CTIs irrespective of CPU bound or
30 * We assume that the non-CPU CTIs are always powered as we do with sinks etc.
32 * We leave the client to figure out if all the CTIs are interconnected with
48 /* quick lookup list for CPU bound CTIs when power handling */
53 * N is the CPU ID. System CTIs will have the name cti_sys<I> where I
H A Dcoresight-cti.h56 * CTI CSSoc 400 has 8 IO triggers - other CTIs can be impl def.
/linux/arch/arm64/boot/dts/hisilicon/
H A Dhi6220-coresight.dtsi368 /* System CTIs */