Searched refs:timestamp (Results 1 – 10 of 10) sorted by relevance
| /trusted-firmware-a/plat/nvidia/tegra/lib/debug/ |
| A D | profiler.c | 45 uint64_t timestamp; member
112 cur->timestamp = mmio_read_32(tmr); in boot_profiler_add_record()
|
| /trusted-firmware-a/include/plat/marvell/armada/a8k/common/ |
| A D | plat_pm_trace.h | 21 unsigned int timestamp; member
|
| /trusted-firmware-a/docs/design/ |
| A D | firmware-design.rst | 2444 By default, the global physical counter is used for the timestamp
2451 A PMF timestamp is uniquely identified across the system via the
2452 timestamp ID or ``tid``. The ``tid`` is composed as follows:
2456 Bits 0-7: The local timestamp identifier.
2485 retrieve a particular timestamp for the given service at runtime.
2493 Capturing a timestamp
2496 PMF timestamps are stored in a per-service timestamp region. On a
2497 system with multiple CPUs, each timestamp is captured and stored
2509 To capture a timestamp in assembly code, the caller should use
2511 calculate the address of where the timestamp would be stored. The
[all …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/design/ |
| A D | firmware-design.rst.txt | 2444 By default, the global physical counter is used for the timestamp
2451 A PMF timestamp is uniquely identified across the system via the
2452 timestamp ID or ``tid``. The ``tid`` is composed as follows:
2456 Bits 0-7: The local timestamp identifier.
2485 retrieve a particular timestamp for the given service at runtime.
2493 Capturing a timestamp
2496 PMF timestamps are stored in a per-service timestamp region. On a
2497 system with multiple CPUs, each timestamp is captured and stored
2509 To capture a timestamp in assembly code, the caller should use
2511 calculate the address of where the timestamp would be stored. The
[all …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/ |
| A D | searchindex.js | 1 …timestamp:[6,8,48,53,63],tispl:118,titl:[125,130,133,134,135,136,137,138,139,140],tl:[6,26,36,44,5…
|
| /trusted-firmware-a/docs/getting_started/ |
| A D | build-options.rst | 297 instrumentation which injects timestamp collection points into TF-A to
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/getting_started/ |
| A D | build-options.rst.txt | 297 instrumentation which injects timestamp collection points into TF-A to
|
| /trusted-firmware-a/docs/build/latex/ |
| A D | trustedfirmware-a.tex | 30381 By default, the global physical counter is used for the timestamp
30389 A PMF timestamp is uniquely identified across the system via the
30433 retrieve a particular timestamp for the given service at runtime.
30443 \subsubsection{Capturing a timestamp}
30444 \label{\detokenize{design/firmware-design:capturing-a-timestamp}}
30447 system with multiple CPUs, each timestamp is captured and stored
30462 To capture a timestamp in assembly code, the caller should use
30464 calculate the address of where the timestamp would be stored. The
30469 \subsubsection{Retrieving a timestamp}
30499 cache invalidate before reading the timestamp. This ensures
[all …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/ |
| A D | change-log.md.txt | 2308 - common: Flush dcache when storing timestamp
3325 - Improved PSCI STAT timestamp collection, including moving accounting for
|
| /trusted-firmware-a/docs/ |
| A D | change-log.md | 2308 - common: Flush dcache when storing timestamp
3325 - Improved PSCI STAT timestamp collection, including moving accounting for
|
Completed in 128 milliseconds