| /arm-trusted-firmware-2.8.0/plat/mediatek/mt8195/drivers/spm/ |
| A D | mt_spm.c | 46 .run = spm_run_rc_bus26m,
54 .run = spm_run_rc_syspll,
62 .run = spm_run_rc_dram,
70 .run = spm_run_rc_cpu_buck_ldo,
|
| /arm-trusted-firmware-2.8.0/plat/mediatek/mt8192/drivers/spm/ |
| A D | mt_spm.c | 51 .run = spm_run_rc_bus26m,
59 .run = spm_run_rc_syspll,
67 .run = spm_run_rc_dram,
75 .run = spm_run_rc_cpu_buck_ldo,
|
| /arm-trusted-firmware-2.8.0/plat/mediatek/mt8186/drivers/spm/ |
| A D | mt_spm.c | 54 .run = spm_run_rc_bus26m,
62 .run = spm_run_rc_syspll,
70 .run = spm_run_rc_dram,
79 .run = spm_run_rc_cpu_buck_ldo,
|
| /arm-trusted-firmware-2.8.0/plat/mediatek/common/lpm/ |
| A D | mt_lp_rm.c | 79 if (((*rc)->run != NULL) && in mt_lp_rm_find_and_run_constraint()
80 ((*rc)->run(cpuid, stateid) == 0)) { in mt_lp_rm_find_and_run_constraint()
|
| A D | mt_lp_rm.h | 25 int (*run)(unsigned int cpu, int stateid); member
|
| /arm-trusted-firmware-2.8.0/docs/getting_started/ |
| A D | docs-build.rst | 70 directory of the project, run the following command to see the supported
72 the command is run from the project root directory, as that would invoke the
86 page for installation instructions. Once installed, run the following script
91 docker run --rm -v $PWD:/TF sphinxdoc/sphinx \
|
| A D | prerequisites.rst | 113 appropriate version of Node.js, run the following **from the root directory of
136 TrustedFirmware.org. To clone this repository from the server, run the following
|
| /arm-trusted-firmware-2.8.0/docs/plat/marvell/armada/ |
| A D | uart-booting.rst | 33 …download images from ``uart-images.tgz.bin`` archive unpack it and for non-secure boot variant run:
63 To download single file image built by ``mrvl_flash`` target at the highest speed, run:
71 ``uart-images.tgz.bin`` archive and then run:
97 To download ``flash-image.bin`` image run:
|
| /arm-trusted-firmware-2.8.0/docs/components/ |
| A D | realm-management-extension.rst | 8 provides instructions on how to build and run TF-A with RME.
46 modified to run BL2 at EL3 when RME is enabled. In addition to this, a
95 This section describes how you can build and run TF-A with RME enabled.
98 The following instructions show you how to build and run TF-A with RME
114 To run the tests, you need an FVP model. Please use the :ref:`latest version
187 Use the following command to run the tests on FVP. TF-A Tests should boot
188 and run the default tests including Realm world tests.
286 Boot and run the RME enabled Linux Kernel
298 Set the FVP option `cache_state_modelled=0` to run Linux based tests much faster.
372 `Running the tests for a 3 world FVP setup`_ to run tests for 4 world setup.
|
| A D | ras.rst | 32 The build option ``RAS_EXTENSION`` when set to ``1`` includes the RAS in run
70 With this information supplied, when the run time firmware receives one of the
197 - ``RAS_EXTENSION=1`` includes the RAS framework in the run time firmware;
|
| A D | ffa-manifest-binding.rst | 134 scheduler. If so, run-time EL must be EL1.
136 - run-time-model
|
| A D | debugfs-design.rst | 67 This interface is embedded into the BL31 run-time payload when selected by build
|
| /arm-trusted-firmware-2.8.0/plat/arm/board/fvp/fdts/ |
| A D | optee_sp_manifest.dts | 30 run-time-model = <1>; /* SP pre-emptible. */
|
| /arm-trusted-firmware-2.8.0/docs/ |
| A D | requirements.txt | 3 # To update, run:
|
| /arm-trusted-firmware-2.8.0/docs/design/ |
| A D | alt-boot-flows.rst | 9 hardware, for example to run silicon soak tests.
53 run-time.
|
| A D | reset-design.rst | 111 address dynamically at run-time, it is possible to set the initial value of the
116 which case the ``bl31.bin`` image must be loaded to its run address in Trusted
117 SRAM and all CPU reset vectors be changed from the default ``0x0`` to this run
|
| /arm-trusted-firmware-2.8.0/docs/plat/ |
| A D | qemu.rst | 10 BL2 edits the Flattened Device Tree, FDT, generated by QEMU at run-time to
149 dependencies, and are run as part of the OpenCI TF-A `daily job`_. To run them
|
| A D | qemu-sbsa.rst | 16 BL2 edits the FDT, generated by QEMU at run-time to add a node describing PSCI
|
| A D | socionext-uniphier.rst | 16 of TF-A run in DRAM.
54 They all run in the DRAM. See :ref:`Firmware Design` for details.
|
| A D | rpi3.rst | 235 to be able to run Windows on ARM64. This option, which is disabled by
267 - ``BL32``: This port can load and run OP-TEE. The OP-TEE image is optional.
361 The following instructions show how to install and run a AArch64 kernel by
367 allows the user to run 64-bit binaries in addition to 32-bit binaries.
|
| /arm-trusted-firmware-2.8.0/docs/design_documents/ |
| A D | cmake_framework.rst | 112 In the development phase first we run CMake, which will generate the buildsystem
114 supported). After this we run the selected build tool which in turn calls the
115 compiler, linker, packaging tool, etc. Finally we can run and debug the output
|
| A D | measured_boot_poc.rst | 33 TF-A with support for Measured Boot enabled (and run it on a Foundation Model)
146 pass the ``-j`` option to make to run the process faster.
148 After this step, you should be ready to run the image.
153 With everything built, you can now run the image:
157 $ make run-only
160 Using ``make run`` will build and run the image and it can be used instead
162 use ``make run-only`` to avoid re-running all the building rules, which
|
| /arm-trusted-firmware-2.8.0/plat/nxp/soc-lx2160a/ |
| A D | soc.def | 82 # for DDR PHY images scratch pad region during BL2 run time)
|
| /arm-trusted-firmware-2.8.0/docs/threat_model/ |
| A D | threat_model_el3_spm.rst | 23 - Focus on the run-time part of the life-cycle (no specific emphasis on boot
87 - Bootloaders (in particular BL1/BL2 if using TF-A) and run-time BL31 are
314 | | state transitions (run-time model). |
439 | | run time model, do input validation. |
445 | | Further FF-A v1.1 guidance about run time models |
|
| A D | threat_model_fvp_r.rst | 42 - Anything otherwise-relevant code running in EL3 is instead run in EL2.
|