Home
last modified time | relevance | path

Searched full:cti (Results 1 – 25 of 59) sorted by relevance

123

/kernel/linux/linux-6.6/arch/arm/include/asm/
Dcti.h41 * struct cti - cross trigger interface struct
42 * @base: mapped virtual address for the cti base
43 * @irq: irq number for the cti
47 * cti struct used to operate cti registers.
49 struct cti { struct
56 * cti_init - initialize the cti instance argument
57 * @cti: cti instance
58 * @base: mapped virtual address for the cti base
59 * @irq: irq number for the cti
64 * @base, @irq and @trig_out to cti.
[all …]
/kernel/linux/linux-5.10/arch/arm/include/asm/
Dcti.h41 * struct cti - cross trigger interface struct
42 * @base: mapped virtual address for the cti base
43 * @irq: irq number for the cti
47 * cti struct used to operate cti registers.
49 struct cti { struct
56 * cti_init - initialize the cti instance argument
57 * @cti: cti instance
58 * @base: mapped virtual address for the cti base
59 * @irq: irq number for the cti
64 * @base, @irq and @trig_out to cti.
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/arm/
Darm,coresight-cti.yaml5 $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
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/
Dcoresight-cti.yaml5 $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
[all …]
Dcoresight.txt48 - Coresight Cross Trigger Interface (CTI):
49 "arm,coresight-cti", "arm,primecell";
50 See coresight-cti.yaml for full CTI definitions.
79 * Required properties for Coresight Cross Trigger Interface (CTI)
80 See coresight-cti.yaml for full CTI definitions.
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-bus-coresight-devices-cti1 What: /sys/bus/coresight/devices/<cti-name>/enable
5 Description: (RW) Enable/Disable the CTI hardware.
7 What: /sys/bus/coresight/devices/<cti-name>/powered
11 Description: (Read) Indicate if the CTI hardware is powered.
13 What: /sys/bus/coresight/devices/<cti-name>/ctmid
19 What: /sys/bus/coresight/devices/<cti-name>/nr_trigger_cons
23 Description: (Read) Number of devices connected to triggers on this CTI
25 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/name
31 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_signals
37 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_types
[all …]
/kernel/linux/linux-6.6/Documentation/ABI/testing/
Dsysfs-bus-coresight-devices-cti1 What: /sys/bus/coresight/devices/<cti-name>/enable
5 Description: (RW) Enable/Disable the CTI hardware.
7 What: /sys/bus/coresight/devices/<cti-name>/powered
11 Description: (Read) Indicate if the CTI hardware is powered.
13 What: /sys/bus/coresight/devices/<cti-name>/ctmid
19 What: /sys/bus/coresight/devices/<cti-name>/nr_trigger_cons
23 Description: (Read) Number of devices connected to triggers on this CTI
25 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/name
31 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_signals
37 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_types
[all …]
/kernel/linux/linux-5.10/arch/arm64/boot/dts/hisilicon/
Dhi6220-coresight.dtsi369 /* CTI 0 - TMC and TPIU connections */
370 cti@f6403000 {
371 compatible = "arm,coresight-cti", "arm,primecell";
378 /* CTI - CPU-0 */
379 cti@f6598000 {
380 compatible = "arm,coresight-cti-v8-arch",
381 "arm,coresight-cti", "arm,primecell";
391 /* CTI - CPU-1 */
392 cti@f6599000 {
393 compatible = "arm,coresight-cti-v8-arch",
[all …]
/kernel/linux/linux-6.6/arch/arm64/boot/dts/hisilicon/
Dhi6220-coresight.dtsi369 /* CTI 0 - TMC and TPIU connections */
370 cti@f6403000 {
371 compatible = "arm,coresight-cti", "arm,primecell";
378 /* CTI - CPU-0 */
379 cti@f6598000 {
380 compatible = "arm,coresight-cti-v8-arch",
381 "arm,coresight-cti", "arm,primecell";
391 /* CTI - CPU-1 */
392 cti@f6599000 {
393 compatible = "arm,coresight-cti-v8-arch",
[all …]
/kernel/linux/linux-5.10/drivers/hwtracing/coresight/
Dcoresight-cti.h22 * 0x000 - 0x144: CTI programming and status
23 * 0xEDC - 0xEF8: CTI integration test.
26 /* CTI programming registers */
41 #define ITCHINACK 0xEDC /* WO CTI CSSoc 400 only*/
42 #define ITTRIGINACK 0xEE0 /* WO CTI CSSoc 400 only*/
45 #define ITCHOUTACK 0xEEC /* RO CTI CSSoc 400 only*/
46 #define ITTRIGOUTACK 0xEF0 /* RO CTI CSSoc 400 only*/
54 * CTI CSSoc 600 has a max of 32 trigger signals per direction.
55 * CTI CSSoc 400 has 8 IO triggers - other CTIs can be impl def.
75 * Trigger connection - connection between a CTI and other (coresight) device
[all …]
Dcoresight-cti-core.c23 #include "coresight-cti.h"
26 * CTI devices can be associated with a PE, or be connected to CoreSight
36 /* net of CTI devices connected via CTM */
52 * CTI naming. CTI bound to cores will have the name cti_cpu<N> where
56 * CTI device name list - for CTI not bound to cores.
68 /* disable CTI before writing registers */ in cti_write_all_hw_regs()
71 /* write the CTI trigger registers */ in cti_write_all_hw_regs()
83 /* re-enable CTI */ in cti_write_all_hw_regs()
123 /* re-enable CTI on CPU when using CPU hotplug */
166 /* disable CTI */ in cti_disable_hw()
[all …]
Dcoresight-cti-platform.c12 #include <dt-bindings/arm/coresight-cti-dt.h>
14 #include "coresight-cti.h"
17 /* Number of CTI signals in the v8 architecturally defined connection */
22 /* CTI device tree trigger connection node keyword */
25 /* CTI device tree connection property keywords */
26 #define CTI_DT_V8ARCH_COMPAT "arm,coresight-cti-v8-arch"
34 #define CTI_DT_CTM_ID "arm,cti-ctm-id"
38 * CTI can be bound to a CPU, or a system device.
51 /* CTI affinity defaults to no cpu */ in of_cti_get_cpu_at_node()
70 * CTI can be bound to a CPU, or a system device.
[all …]
DMakefile23 obj-$(CONFIG_CORESIGHT_CTI) += coresight-cti.o
24 coresight-cti-y := coresight-cti-core.o coresight-cti-platform.o \
25 coresight-cti-sysfs.o
DKconfig145 tristate "CoreSight Cross Trigger Interface (CTI) driver"
148 This driver provides support for CoreSight CTI and CTM components.
151 inject events into the trace stream. CTI also provides a software
157 module will be called coresight-cti.
160 bool "Access CTI CoreSight Integration Registers"
165 CTI trigger connections between this and other devices.These
/kernel/linux/linux-6.6/drivers/hwtracing/coresight/
Dcoresight-cti.h22 * 0x000 - 0x144: CTI programming and status
23 * 0xEDC - 0xEF8: CTI integration test.
26 /* CTI programming registers */
41 #define ITCHINACK 0xEDC /* WO CTI CSSoc 400 only*/
42 #define ITTRIGINACK 0xEE0 /* WO CTI CSSoc 400 only*/
45 #define ITCHOUTACK 0xEEC /* RO CTI CSSoc 400 only*/
46 #define ITTRIGOUTACK 0xEF0 /* RO CTI CSSoc 400 only*/
54 * CTI CSSoc 600 has a max of 32 trigger signals per direction.
55 * CTI CSSoc 400 has 8 IO triggers - other CTIs can be impl def.
75 * Trigger connection - connection between a CTI and other (coresight) device
[all …]
Dcoresight-cti-core.c23 #include "coresight-cti.h"
26 * CTI devices can be associated with a PE, or be connected to CoreSight
36 /* net of CTI devices connected via CTM */
52 * CTI naming. CTI bound to cores will have the name cti_cpu<N> where
56 * CTI device name list - for CTI not bound to cores.
68 /* disable CTI before writing registers */ in cti_write_all_hw_regs()
71 /* write the CTI trigger registers */ in cti_write_all_hw_regs()
83 /* re-enable CTI */ in cti_write_all_hw_regs()
123 /* re-enable CTI on CPU when using CPU hotplug */
174 /* disable CTI */ in cti_disable_hw()
[all …]
Dcoresight-cti-platform.c12 #include <dt-bindings/arm/coresight-cti-dt.h>
14 #include "coresight-cti.h"
17 /* Number of CTI signals in the v8 architecturally defined connection */
22 /* CTI device tree trigger connection node keyword */
25 /* CTI device tree connection property keywords */
26 #define CTI_DT_V8ARCH_COMPAT "arm,coresight-cti-v8-arch"
34 #define CTI_DT_CTM_ID "arm,cti-ctm-id"
38 * CTI can be bound to a CPU, or a system device.
51 /* CTI affinity defaults to no cpu */ in of_cti_get_cpu_at_node()
70 * CTI can be bound to a CPU, or a system device.
[all …]
DMakefile26 obj-$(CONFIG_CORESIGHT_CTI) += coresight-cti.o
30 coresight-cti-y := coresight-cti-core.o coresight-cti-platform.o \
31 coresight-cti-sysfs.o
DKconfig167 tristate "CoreSight Cross Trigger Interface (CTI) driver"
170 This driver provides support for CoreSight CTI and CTM components.
173 inject events into the trace stream. CTI also provides a software
179 module will be called coresight-cti.
182 bool "Access CTI CoreSight Integration Registers"
187 CTI trigger connections between this and other devices.These
/kernel/linux/linux-5.10/Documentation/trace/coresight/
Dcoresight-ect.rst4 CoreSight Embedded Cross Trigger (CTI & CTM).
13 The CoreSight Cross Trigger Interface (CTI) is a hardware device that takes
21 0 C 0----------->: : +======>(other CTI channel IO)
24 0000000 : CTI :<=========>*CTM*<====>: CTI :---+
30 The CTI driver enables the programming of the CTI to attach triggers to
34 activating connected output triggers there, unless filtered by the CTI
38 programming registers in the CTI.
53 All the CTI devices are associated with a CTM. On many systems there will be a
57 CTI devices that are interconnected via a given CTM.
62 The CTI devices appear on the existing CoreSight bus alongside the other
[all …]
/kernel/linux/linux-6.6/Documentation/trace/coresight/
Dcoresight-ect.rst4 CoreSight Embedded Cross Trigger (CTI & CTM).
13 The CoreSight Cross Trigger Interface (CTI) is a hardware device that takes
21 0 C 0----------->: : +======>(other CTI channel IO)
24 0000000 : CTI :<=========>*CTM*<====>: CTI :---+
30 The CTI driver enables the programming of the CTI to attach triggers to
34 activating connected output triggers there, unless filtered by the CTI
38 programming registers in the CTI.
53 All the CTI devices are associated with a CTM. On many systems there will be a
57 CTI devices that are interconnected via a given CTM.
62 The CTI devices appear on the existing CoreSight bus alongside the other
[all …]
/kernel/linux/linux-6.6/tools/perf/pmu-events/arch/arm64/arm/neoverse-n2-v2/
Dtrace.json24 …"PublicDescription": "This event is generated each time an event is signaled on CTI output trigger…
28 …"PublicDescription": "This event is generated each time an event is signaled on CTI output trigger…
32 …"PublicDescription": "This event is generated each time an event is signaled on CTI output trigger…
36 …"PublicDescription": "This event is generated each time an event is signaled on CTI output trigger…
/kernel/linux/linux-6.6/arch/arm64/boot/dts/arm/
Djuno-base.dtsi293 cti0: cti@22020000 {
294 compatible = "arm,coresight-cti-v8-arch", "arm,coresight-cti",
365 cti1: cti@22120000 {
366 compatible = "arm,coresight-cti-v8-arch", "arm,coresight-cti",
402 cti2: cti@23020000 {
403 compatible = "arm,coresight-cti-v8-arch", "arm,coresight-cti",
486 cti3: cti@23120000 {
487 compatible = "arm,coresight-cti-v8-arch", "arm,coresight-cti",
523 cti4: cti@23220000 {
524 compatible = "arm,coresight-cti-v8-arch", "arm,coresight-cti",
[all …]
/kernel/linux/linux-6.6/arch/sparc/kernel/
Dsyscalls.S218 bgeu,pn %xcc, linux_sparc_ni_syscall ! CTI
229 bne,pn %icc, linux_syscall_trace32 ! CTI
231 5: call %l7 ! CTI Group brk forced
242 bgeu,pn %xcc, linux_sparc_ni_syscall ! CTI
253 bne,pn %icc, linux_syscall_trace ! CTI Group
255 2: call %l7 ! CTI Group brk forced
/kernel/linux/linux-5.10/arch/sparc/kernel/
Dsyscalls.S218 bgeu,pn %xcc, linux_sparc_ni_syscall ! CTI
229 bne,pn %icc, linux_syscall_trace32 ! CTI
231 5: call %l7 ! CTI Group brk forced
242 bgeu,pn %xcc, linux_sparc_ni_syscall ! CTI
253 bne,pn %icc, linux_syscall_trace ! CTI Group
255 2: call %l7 ! CTI Group brk forced

123