2019-05-19 20:07:45 +08:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2015-03-31 04:13:36 +08:00
|
|
|
#
|
|
|
|
|
# Coresight configuration
|
|
|
|
|
#
|
|
|
|
|
menuconfig CORESIGHT
|
|
|
|
|
bool "CoreSight Tracing Support"
|
2019-11-05 02:12:49 +08:00
|
|
|
depends on ARM || ARM64
|
2019-06-20 03:53:17 +08:00
|
|
|
depends on OF || ACPI
|
2015-03-31 04:13:36 +08:00
|
|
|
select ARM_AMBA
|
2016-02-18 08:51:57 +08:00
|
|
|
select PERF_EVENTS
|
2015-03-31 04:13:36 +08:00
|
|
|
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
|
2015-12-17 23:47:02 +08:00
|
|
|
specification and configure the right series of components when a
|
2015-03-31 04:13:36 +08:00
|
|
|
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.
|
|
|
|
|
|
2018-07-12 03:40:31 +08:00
|
|
|
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.
|
|
|
|
|
|
2015-03-31 04:13:36 +08:00
|
|
|
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.
|
2015-05-14 00:34:09 +08:00
|
|
|
|
|
|
|
|
config CORESIGHT_SOURCE_ETM4X
|
|
|
|
|
bool "CoreSight Embedded Trace Macrocell 4.x driver"
|
|
|
|
|
depends on ARM64
|
|
|
|
|
select CORESIGHT_LINKS_AND_SINKS
|
2019-04-26 03:52:52 +08:00
|
|
|
select PID_IN_CONTEXTIDR
|
2015-05-14 00:34:09 +08:00
|
|
|
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.
|
|
|
|
|
|
2016-05-04 01:33:40 +08:00
|
|
|
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
|
|
|
|
|
|
coresight: add support for CPU debug module
Coresight includes debug module and usually the module connects with CPU
debug logic. ARMv8 architecture reference manual (ARM DDI 0487A.k) has
description for related info in "Part H: External Debug".
Chapter H7 "The Sample-based Profiling Extension" introduces several
sampling registers, e.g. we can check program counter value with
combined CPU exception level, secure state, etc. So this is helpful for
analysis CPU lockup scenarios, e.g. if one CPU has run into infinite
loop with IRQ disabled. In this case the CPU cannot switch context and
handle any interrupt (including IPIs), as the result it cannot handle
SMP call for stack dump.
This patch is to enable coresight debug module, so firstly this driver
is to bind apb clock for debug module and this is to ensure the debug
module can be accessed from program or external debugger. And the driver
uses sample-based registers for debug purpose, e.g. when system triggers
panic, the driver will dump program counter and combined context
registers (EDCIDSR, EDVIDSR); by parsing context registers so can
quickly get to know CPU secure state, exception level, etc.
Some of the debug module registers are located in CPU power domain, so
this requires the CPU power domain stays on when access related debug
registers, but the power management for CPU power domain is quite
dependent on SoC integration for power management. For the platforms
which with sane power controller implementations, this driver follows
the method to set EDPRCR to try to pull the CPU out of low power state
and then set 'no power down request' bit so the CPU has no chance to
lose power.
If the SoC has not followed up this design well for power management
controller, the user should use the command line parameter or sysfs
to constrain all or partial idle states to ensure the CPU power
domain is enabled and access coresight CPU debug component safely.
Signed-off-by: Leo Yan <leo.yan@linaro.org>
Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-06-06 04:15:16 +08:00
|
|
|
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
|
2019-08-01 04:08:48 +08:00
|
|
|
properly, please refer Documentation/trace/coresight-cpu-debug.rst
|
coresight: add support for CPU debug module
Coresight includes debug module and usually the module connects with CPU
debug logic. ARMv8 architecture reference manual (ARM DDI 0487A.k) has
description for related info in "Part H: External Debug".
Chapter H7 "The Sample-based Profiling Extension" introduces several
sampling registers, e.g. we can check program counter value with
combined CPU exception level, secure state, etc. So this is helpful for
analysis CPU lockup scenarios, e.g. if one CPU has run into infinite
loop with IRQ disabled. In this case the CPU cannot switch context and
handle any interrupt (including IPIs), as the result it cannot handle
SMP call for stack dump.
This patch is to enable coresight debug module, so firstly this driver
is to bind apb clock for debug module and this is to ensure the debug
module can be accessed from program or external debugger. And the driver
uses sample-based registers for debug purpose, e.g. when system triggers
panic, the driver will dump program counter and combined context
registers (EDCIDSR, EDVIDSR); by parsing context registers so can
quickly get to know CPU secure state, exception level, etc.
Some of the debug module registers are located in CPU power domain, so
this requires the CPU power domain stays on when access related debug
registers, but the power management for CPU power domain is quite
dependent on SoC integration for power management. For the platforms
which with sane power controller implementations, this driver follows
the method to set EDPRCR to try to pull the CPU out of low power state
and then set 'no power down request' bit so the CPU has no chance to
lose power.
If the SoC has not followed up this design well for power management
controller, the user should use the command line parameter or sysfs
to constrain all or partial idle states to ensure the CPU power
domain is enabled and access coresight CPU debug component safely.
Signed-off-by: Leo Yan <leo.yan@linaro.org>
Reviewed-by: Suzuki K Poulose <suzuki.poulose@arm.com>
Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
2017-06-06 04:15:16 +08:00
|
|
|
for detailed description and the example for usage.
|
|
|
|
|
|
2020-03-21 00:52:52 +08:00
|
|
|
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.
|
|
|
|
|
|
2020-03-21 00:52:54 +08:00
|
|
|
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.
|
2015-03-31 04:13:36 +08:00
|
|
|
endif
|