Searched refs:run (Results 1 – 25 of 53) sorted by relevance
123
| /trusted-firmware-a-latest/plat/mediatek/mt8195/drivers/spm/ |
| 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,
|
| /trusted-firmware-a-latest/plat/mediatek/mt8192/drivers/spm/ |
| 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,
|
| /trusted-firmware-a-latest/plat/mediatek/mt8186/drivers/spm/ |
| 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,
|
| /trusted-firmware-a-latest/plat/mediatek/drivers/spm/mt8188/ |
| D | mt_spm.c | 103 .run = spm_run_rc_bus26m,
112 .run = spm_run_rc_syspll,
121 .run = spm_run_rc_dram,
130 .run = spm_run_rc_cpu_buck_ldo,
|
| /trusted-firmware-a-latest/docs/getting_started/ |
| D | docs-build.rst | 62 poetry run make doc
70 directory of the project, run the following command to see the supported
75 poetry run make -C docs help
93 Once all the dependencies are installed, run the command ``poetry run make -C
100 The command ``poetry run`` used in the steps above executes the input command
123 page for installation instructions. Once installed, run the following script
128 docker run --rm -v $PWD:/tf-a sphinxdoc/sphinx \
132 ~/.local/bin/poetry install && ~/.local/bin/poetry run make doc'
|
| D | prerequisites.rst | 104 reproduce a Python environment to build documentation and run analysis tools.
126 appropriate version of Node.js, run the following **from the root directory of
149 TrustedFirmware.org. To clone this repository from the server, run the following
|
| /trusted-firmware-a-latest/docs/tools/ |
| D | memory-layout-tool.rst | 32 poetry run memory --help
44 $ poetry run memory -s
110 For more detailed help instructions, run:
114 poetry run memory --help
126 $ poetry run memory -f
159 $ poetry run memory -t
212 $ poetry run memory -t --depth 2
|
| /trusted-firmware-a-latest/docs/plat/marvell/armada/ |
| 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:
|
| /trusted-firmware-a-latest/plat/mediatek/common/lpm/ |
| D | mt_lp_rm.c | 90 if ((rc != NULL) && (rc->run != NULL)) { in mt_lp_rm_do_constraint()
91 res = rc->run(cpuid, stateid); in mt_lp_rm_do_constraint()
|
| /trusted-firmware-a-latest/plat/mediatek/include/lpm/ |
| D | mt_lp_rm.h | 45 int (*run)(unsigned int cpu, int stateid); member
|
| /trusted-firmware-a-latest/plat/arm/board/fvp/fdts/ |
| D | optee_sp_manifest.dts | 30 run-time-model = <1>; /* SP pre-emptible. */
|
| /trusted-firmware-a-latest/docs/components/ |
| 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
118 To run the tests, you need an FVP model. Please use the :ref:`latest version
181 run at R-EL2.
228 Use the following command to run the tests on FVP.
298 Tips to boot and run Linux faster on the FVP :
378 build to run SP tests.
399 :ref:`4. Running FVP for 3 world setup <fvp_3_world_cmd>` to run tests for
|
| /trusted-firmware-a-latest/docs/design/ |
| D | alt-boot-flows.rst | 9 hardware, for example to run silicon soak tests.
53 run-time.
|
| 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
|
| /trusted-firmware-a-latest/docs/design_documents/ |
| 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
|
| D | measured_boot_poc.rst | 35 TF-A with support for Measured Boot enabled (and run it on a Foundation Model)
148 pass the ``-j`` option to make to run the process faster.
150 After this step, you should be ready to run the image.
155 With everything built, you can now run the image:
159 $ make run-only
162 Using ``make run`` will build and run the image and it can be used instead
164 use ``make run-only`` to avoid re-running all the building rules, which
|
| /trusted-firmware-a-latest/docs/plat/ |
| D | qemu.rst | 10 BL2 edits the Flattened Device Tree, FDT, generated by QEMU at run-time to
168 dependencies, and are run as part of the OpenCI TF-A `daily job`_. To run them
|
| D | qemu-sbsa.rst | 16 BL2 edits the FDT, generated by QEMU at run-time to add a node describing PSCI
|
| D | socionext-uniphier.rst | 16 of TF-A run in DRAM.
54 They all run in the DRAM. See :ref:`Firmware Design` for details.
|
| 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.
356 The following instructions show how to install and run a AArch64 kernel by
362 allows the user to run 64-bit binaries in addition to 32-bit binaries.
|
| D | rpi4.rst | 60 run after the SoC gets its power. The on-chip Boot ROM loads the next stage
|
| /trusted-firmware-a-latest/plat/nxp/soc-lx2160a/ |
| D | soc.def | 82 # for DDR PHY images scratch pad region during BL2 run time)
|
| /trusted-firmware-a-latest/docs/threat_model/ |
| D | threat_model_el3_spm.rst | 24 - Focus on the run-time part of the life-cycle (no specific emphasis on boot
88 - Bootloaders (in particular BL1/BL2 if using TF-A) and run-time BL31 are
316 | | state transitions (run-time model). |
441 | | run time model, do input validation. |
447 | | Further FF-A v1.1 guidance about run time models |
|
| D | threat_model_fvp_r.rst | 42 - Anything otherwise-relevant code running in EL3 is instead run in EL2.
|
| /trusted-firmware-a-latest/docs/plat/arm/arm_fpga/ |
| D | index.rst | 93 …fpga-run ... -m bl31.axf -l auto -m Image -l 0x80080000 -m initrd.gz -l 0x84000000 -m cmdline.txt …
|
123
