mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-28 11:18:45 +07:00
b5213376c2
Adds in sysfs programming support for the CTI function register sets. Allows direct manipulation of channel / trigger association registers. Signed-off-by: Mike Leach <mike.leach@linaro.org> Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com> Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org> Link: https://lore.kernel.org/r/20200320165303.13681-4-mathieu.poirier@linaro.org Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
135 lines
5.4 KiB
Plaintext
135 lines
5.4 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0-only
|
|
#
|
|
# Coresight configuration
|
|
#
|
|
menuconfig CORESIGHT
|
|
bool "CoreSight Tracing Support"
|
|
depends on ARM || ARM64
|
|
depends on OF || ACPI
|
|
select ARM_AMBA
|
|
select PERF_EVENTS
|
|
help
|
|
This framework provides a kernel interface for the CoreSight debug
|
|
and trace drivers to register themselves with. It's intended to build
|
|
a topological view of the CoreSight components based on a DT
|
|
specification and configure the right series of components when a
|
|
trace source gets enabled.
|
|
|
|
if CORESIGHT
|
|
config CORESIGHT_LINKS_AND_SINKS
|
|
bool "CoreSight Link and Sink drivers"
|
|
help
|
|
This enables support for CoreSight link and sink drivers that are
|
|
responsible for transporting and collecting the trace data
|
|
respectively. Link and sinks are dynamically aggregated with a trace
|
|
entity at run time to form a complete trace path.
|
|
|
|
config CORESIGHT_LINK_AND_SINK_TMC
|
|
bool "Coresight generic TMC driver"
|
|
depends on CORESIGHT_LINKS_AND_SINKS
|
|
help
|
|
This enables support for the Trace Memory Controller driver.
|
|
Depending on its configuration the device can act as a link (embedded
|
|
trace router - ETR) or sink (embedded trace FIFO). The driver
|
|
complies with the generic implementation of the component without
|
|
special enhancement or added features.
|
|
|
|
config CORESIGHT_CATU
|
|
bool "Coresight Address Translation Unit (CATU) driver"
|
|
depends on CORESIGHT_LINK_AND_SINK_TMC
|
|
help
|
|
Enable support for the Coresight Address Translation Unit (CATU).
|
|
CATU supports a scatter gather table of 4K pages, with forward/backward
|
|
lookup. CATU helps TMC ETR to use a large physically non-contiguous trace
|
|
buffer by translating the addresses used by ETR to the physical address
|
|
by looking up the provided table. CATU can also be used in pass-through
|
|
mode where the address is not translated.
|
|
|
|
config CORESIGHT_SINK_TPIU
|
|
bool "Coresight generic TPIU driver"
|
|
depends on CORESIGHT_LINKS_AND_SINKS
|
|
help
|
|
This enables support for the Trace Port Interface Unit driver,
|
|
responsible for bridging the gap between the on-chip coresight
|
|
components and a trace for bridging the gap between the on-chip
|
|
coresight components and a trace port collection engine, typically
|
|
connected to an external host for use case capturing more traces than
|
|
the on-board coresight memory can handle.
|
|
|
|
config CORESIGHT_SINK_ETBV10
|
|
bool "Coresight ETBv1.0 driver"
|
|
depends on CORESIGHT_LINKS_AND_SINKS
|
|
help
|
|
This enables support for the Embedded Trace Buffer version 1.0 driver
|
|
that complies with the generic implementation of the component without
|
|
special enhancement or added features.
|
|
|
|
config CORESIGHT_SOURCE_ETM3X
|
|
bool "CoreSight Embedded Trace Macrocell 3.x driver"
|
|
depends on !ARM64
|
|
select CORESIGHT_LINKS_AND_SINKS
|
|
help
|
|
This driver provides support for processor ETM3.x and PTM1.x modules,
|
|
which allows tracing the instructions that a processor is executing
|
|
This is primarily useful for instruction level tracing. Depending
|
|
the ETM version data tracing may also be available.
|
|
|
|
config CORESIGHT_SOURCE_ETM4X
|
|
bool "CoreSight Embedded Trace Macrocell 4.x driver"
|
|
depends on ARM64
|
|
select CORESIGHT_LINKS_AND_SINKS
|
|
select PID_IN_CONTEXTIDR
|
|
help
|
|
This driver provides support for the ETM4.x tracer module, tracing the
|
|
instructions that a processor is executing. This is primarily useful
|
|
for instruction level tracing. Depending on the implemented version
|
|
data tracing may also be available.
|
|
|
|
config CORESIGHT_STM
|
|
bool "CoreSight System Trace Macrocell driver"
|
|
depends on (ARM && !(CPU_32v3 || CPU_32v4 || CPU_32v4T)) || ARM64
|
|
select CORESIGHT_LINKS_AND_SINKS
|
|
select STM
|
|
help
|
|
This driver provides support for hardware assisted software
|
|
instrumentation based tracing. This is primarily used for
|
|
logging useful software events or data coming from various entities
|
|
in the system, possibly running different OSs
|
|
|
|
config CORESIGHT_CPU_DEBUG
|
|
tristate "CoreSight CPU Debug driver"
|
|
depends on ARM || ARM64
|
|
depends on DEBUG_FS
|
|
help
|
|
This driver provides support for coresight debugging module. This
|
|
is primarily used to dump sample-based profiling registers when
|
|
system triggers panic, the driver will parse context registers so
|
|
can quickly get to know program counter (PC), secure state,
|
|
exception level, etc. Before use debugging functionality, platform
|
|
needs to ensure the clock domain and power domain are enabled
|
|
properly, please refer Documentation/trace/coresight-cpu-debug.rst
|
|
for detailed description and the example for usage.
|
|
|
|
config CORESIGHT_CTI
|
|
bool "CoreSight Cross Trigger Interface (CTI) driver"
|
|
depends on ARM || ARM64
|
|
help
|
|
This driver provides support for CoreSight CTI and CTM components.
|
|
These provide hardware triggering events between CoreSight trace
|
|
source and sink components. These can be used to halt trace or
|
|
inject events into the trace stream. CTI also provides a software
|
|
control to trigger the same halt events. This can provide fast trace
|
|
halt compared to disabling sources and sinks normally in driver
|
|
software.
|
|
|
|
config CORESIGHT_CTI_INTEGRATION_REGS
|
|
bool "Access CTI CoreSight Integration Registers"
|
|
depends on CORESIGHT_CTI
|
|
help
|
|
This option adds support for the CoreSight integration registers on
|
|
this device. The integration registers allow the exploration of the
|
|
CTI trigger connections between this and other devices.These
|
|
registers are not used in normal operation and can leave devices in
|
|
an inconsistent state.
|
|
endif
|