Home
last modified time | relevance | path

Searched refs:timestamp (Results 1 – 6 of 6) sorted by relevance

/trusted-firmware-a-latest/plat/nvidia/tegra/lib/debug/
Dprofiler.c45 uint64_t timestamp; member
112 cur->timestamp = mmio_read_32(tmr); in boot_profiler_add_record()
/trusted-firmware-a-latest/include/plat/marvell/armada/a8k/common/
Dplat_pm_trace.h21 unsigned int timestamp; member
/trusted-firmware-a-latest/docs/perf/
Dpsci-performance-instr.rst85 around the PMF to provide timestamp data. Although the service is not
108 The timestamp during entry into the handler is captured as early as possible
110 timestamps are stored in memory for later retrieval. The exit timestamp is
/trusted-firmware-a-latest/docs/design/
Dfirmware-design.rst2564 By default, the global physical counter is used for the timestamp
2571 A PMF timestamp is uniquely identified across the system via the
2572 timestamp ID or ``tid``. The ``tid`` is composed as follows:
2576 Bits 0-7: The local timestamp identifier.
2585 #. The local timestamp identifier. This identifier is unique within a given
2599 PMF_STORE_ENABLE: The timestamp is stored in memory for later retrieval.
2600 PMF_DUMP_ENABLE: The timestamp is dumped on the serial console.
2605 retrieve a particular timestamp for the given service at runtime.
2613 Capturing a timestamp
2616 PMF timestamps are stored in a per-service timestamp region. On a
[all …]
/trusted-firmware-a-latest/docs/getting_started/
Dbuild-options.rst440 instrumentation which injects timestamp collection points into TF-A to
/trusted-firmware-a-latest/docs/
Dchange-log.md6584 - common: Flush dcache when storing timestamp
7601 - Improved PSCI STAT timestamp collection, including moving accounting for