1 # SPDX-License-Identifier: GPL-2.0-only
3 # Coresight configuration
6 bool "CoreSight Tracing Support"
7 depends on ARM || ARM64
12 This framework provides a kernel interface for the CoreSight debug
13 and trace drivers to register themselves with. It's intended to build
14 a topological view of the CoreSight components based on a DT
15 specification and configure the right series of components when a
16 trace source gets enabled.
19 config CORESIGHT_LINKS_AND_SINKS
20 bool "CoreSight Link and Sink drivers"
22 This enables support for CoreSight link and sink drivers that are
23 responsible for transporting and collecting the trace data
24 respectively. Link and sinks are dynamically aggregated with a trace
25 entity at run time to form a complete trace path.
27 config CORESIGHT_LINK_AND_SINK_TMC
28 bool "Coresight generic TMC driver"
29 depends on CORESIGHT_LINKS_AND_SINKS
31 This enables support for the Trace Memory Controller driver.
32 Depending on its configuration the device can act as a link (embedded
33 trace router - ETR) or sink (embedded trace FIFO). The driver
34 complies with the generic implementation of the component without
35 special enhancement or added features.
38 bool "Coresight Address Translation Unit (CATU) driver"
39 depends on CORESIGHT_LINK_AND_SINK_TMC
41 Enable support for the Coresight Address Translation Unit (CATU).
42 CATU supports a scatter gather table of 4K pages, with forward/backward
43 lookup. CATU helps TMC ETR to use a large physically non-contiguous trace
44 buffer by translating the addresses used by ETR to the physical address
45 by looking up the provided table. CATU can also be used in pass-through
46 mode where the address is not translated.
48 config CORESIGHT_SINK_TPIU
49 bool "Coresight generic TPIU driver"
50 depends on CORESIGHT_LINKS_AND_SINKS
52 This enables support for the Trace Port Interface Unit driver,
53 responsible for bridging the gap between the on-chip coresight
54 components and a trace for bridging the gap between the on-chip
55 coresight components and a trace port collection engine, typically
56 connected to an external host for use case capturing more traces than
57 the on-board coresight memory can handle.
59 config CORESIGHT_SINK_ETBV10
60 bool "Coresight ETBv1.0 driver"
61 depends on CORESIGHT_LINKS_AND_SINKS
63 This enables support for the Embedded Trace Buffer version 1.0 driver
64 that complies with the generic implementation of the component without
65 special enhancement or added features.
67 config CORESIGHT_SOURCE_ETM3X
68 bool "CoreSight Embedded Trace Macrocell 3.x driver"
70 select CORESIGHT_LINKS_AND_SINKS
72 This driver provides support for processor ETM3.x and PTM1.x modules,
73 which allows tracing the instructions that a processor is executing
74 This is primarily useful for instruction level tracing. Depending
75 the ETM version data tracing may also be available.
77 config CORESIGHT_SOURCE_ETM4X
78 bool "CoreSight Embedded Trace Macrocell 4.x driver"
80 select CORESIGHT_LINKS_AND_SINKS
81 select PID_IN_CONTEXTIDR
83 This driver provides support for the ETM4.x tracer module, tracing the
84 instructions that a processor is executing. This is primarily useful
85 for instruction level tracing. Depending on the implemented version
86 data tracing may also be available.
89 bool "CoreSight System Trace Macrocell driver"
90 depends on (ARM && !(CPU_32v3 || CPU_32v4 || CPU_32v4T)) || ARM64
91 select CORESIGHT_LINKS_AND_SINKS
94 This driver provides support for hardware assisted software
95 instrumentation based tracing. This is primarily used for
96 logging useful software events or data coming from various entities
97 in the system, possibly running different OSs
99 config CORESIGHT_CPU_DEBUG
100 tristate "CoreSight CPU Debug driver"
101 depends on ARM || ARM64
104 This driver provides support for coresight debugging module. This
105 is primarily used to dump sample-based profiling registers when
106 system triggers panic, the driver will parse context registers so
107 can quickly get to know program counter (PC), secure state,
108 exception level, etc. Before use debugging functionality, platform
109 needs to ensure the clock domain and power domain are enabled
110 properly, please refer Documentation/trace/coresight-cpu-debug.rst
111 for detailed description and the example for usage.