Home
last modified time | relevance | path

Searched refs:PSCI_VERSION (Results 1 – 7 of 7) sorted by relevance

/trusted-firmware-a-3.6.0-3.5.0/docs/security_advisories/
Dsecurity-advisory-tfv-6.rst68 is more efficient than calling an arbitrary SMC (for example ``PSCI_VERSION``).
73 On Juno R1 we measured the round trip latency for both the ``PSCI_VERSION`` and
89 | ``PSCI_VERSION`` baseline (without PRs in this advisory) | 515 |
91 | ``PSCI_VERSION`` baseline (with PRs in this advisory) | 527 |
93 | ``PSCI_VERSION`` with "MMU disable/enable" | 930 |
97 | ``PSCI_VERSION`` with "BPIALL at AArch32 Secure-EL1" | 1276 |
/trusted-firmware-a-3.6.0-3.5.0/include/lib/psci/
Dpsci.h43 #define PSCI_VERSION U(0x84000000) macro
/trusted-firmware-a-3.6.0-3.5.0/lib/psci/
Dpsci_private.h25 (define_psci_cap(PSCI_VERSION) | \
Dpsci_main.c457 case PSCI_VERSION: in psci_smc_handler()
/trusted-firmware-a-3.6.0-3.5.0/docs/perf/
Dpsci-performance-juno.rst386 ``PSCI_VERSION`` on all CPUs in parallel
389 Since very little code is associated with ``PSCI_VERSION``, this test
/trusted-firmware-a-3.6.0-3.5.0/docs/design/
Dfirmware-design.rst1024 | ``PSCI_VERSION`` | Yes | The version returned is 1.1 |
/trusted-firmware-a-3.6.0-3.5.0/docs/
Dchange-log.md7762 - PSCI API calls `AFFINITY_INFO` & `PSCI_VERSION` have now been tested (to a
7845 - PSCI API calls `AFFINITY_INFO` & `PSCI_VERSION` are implemented but have not