1# SPDX-License-Identifier: GPL-2.0-only 2# 3# Coresight configuration 4# 5menuconfig CORESIGHT 6 bool "CoreSight Tracing Support" 7 depends on ARM || ARM64 8 depends on OF || ACPI 9 select ARM_AMBA 10 select PERF_EVENTS 11 help 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. 17 18if CORESIGHT 19config CORESIGHT_LINKS_AND_SINKS 20 bool "CoreSight Link and Sink drivers" 21 help 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. 26 27config CORESIGHT_LINK_AND_SINK_TMC 28 bool "Coresight generic TMC driver" 29 depends on CORESIGHT_LINKS_AND_SINKS 30 help 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. 36 37config CORESIGHT_CATU 38 bool "Coresight Address Translation Unit (CATU) driver" 39 depends on CORESIGHT_LINK_AND_SINK_TMC 40 help 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. 47 48config CORESIGHT_SINK_TPIU 49 bool "Coresight generic TPIU driver" 50 depends on CORESIGHT_LINKS_AND_SINKS 51 help 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. 58 59config CORESIGHT_SINK_ETBV10 60 bool "Coresight ETBv1.0 driver" 61 depends on CORESIGHT_LINKS_AND_SINKS 62 help 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. 66 67config CORESIGHT_SOURCE_ETM3X 68 tristate "CoreSight Embedded Trace Macrocell 3.x driver" 69 depends on !ARM64 70 select CORESIGHT_LINKS_AND_SINKS 71 help 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. 76 77 To compile this driver as a module, choose M here: the 78 module will be called coresight-etm3x. 79 80config CORESIGHT_SOURCE_ETM4X 81 tristate "CoreSight Embedded Trace Macrocell 4.x driver" 82 depends on ARM64 83 select CORESIGHT_LINKS_AND_SINKS 84 select PID_IN_CONTEXTIDR 85 help 86 This driver provides support for the ETM4.x tracer module, tracing the 87 instructions that a processor is executing. This is primarily useful 88 for instruction level tracing. Depending on the implemented version 89 data tracing may also be available. 90 91 To compile this driver as a module, choose M here: the 92 module will be called coresight-etm4x. 93 94config CORESIGHT_STM 95 tristate "CoreSight System Trace Macrocell driver" 96 depends on (ARM && !(CPU_32v3 || CPU_32v4 || CPU_32v4T)) || ARM64 97 select CORESIGHT_LINKS_AND_SINKS 98 select STM 99 help 100 This driver provides support for hardware assisted software 101 instrumentation based tracing. This is primarily used for 102 logging useful software events or data coming from various entities 103 in the system, possibly running different OSs 104 105 To compile this driver as a module, choose M here: the 106 module will be called coresight-stm. 107 108config CORESIGHT_CPU_DEBUG 109 tristate "CoreSight CPU Debug driver" 110 depends on ARM || ARM64 111 depends on DEBUG_FS 112 help 113 This driver provides support for coresight debugging module. This 114 is primarily used to dump sample-based profiling registers when 115 system triggers panic, the driver will parse context registers so 116 can quickly get to know program counter (PC), secure state, 117 exception level, etc. Before use debugging functionality, platform 118 needs to ensure the clock domain and power domain are enabled 119 properly, please refer Documentation/trace/coresight/coresight-cpu-debug.rst 120 for detailed description and the example for usage. 121 122 To compile this driver as a module, choose M here: the 123 module will be called coresight-cpu-debug. 124 125config CORESIGHT_CTI 126 bool "CoreSight Cross Trigger Interface (CTI) driver" 127 depends on ARM || ARM64 128 help 129 This driver provides support for CoreSight CTI and CTM components. 130 These provide hardware triggering events between CoreSight trace 131 source and sink components. These can be used to halt trace or 132 inject events into the trace stream. CTI also provides a software 133 control to trigger the same halt events. This can provide fast trace 134 halt compared to disabling sources and sinks normally in driver 135 software. 136 137config CORESIGHT_CTI_INTEGRATION_REGS 138 bool "Access CTI CoreSight Integration Registers" 139 depends on CORESIGHT_CTI 140 help 141 This option adds support for the CoreSight integration registers on 142 this device. The integration registers allow the exploration of the 143 CTI trigger connections between this and other devices.These 144 registers are not used in normal operation and can leave devices in 145 an inconsistent state. 146endif 147