| /trusted-firmware-a/drivers/marvell/ |
| A D | cache_llc.c | 116 uint32_t tc, way, ways_to_allocate; in llc_sram_enable() local
135 for (way = 0; way < ways_to_allocate; way++) { in llc_sram_enable()
140 LLC_BLK_ALOC_WAY_ID(way)); in llc_sram_enable()
|
| /trusted-firmware-a/include/drivers/marvell/ |
| A D | cache_llc.h | 40 #define LLC_BLK_ALOC_WAY_ID(way) ((way) & 0x1f) argument
|
| /trusted-firmware-a/docs/build/latex/ |
| A D | sphinxlatexstylepage.sty | 33 % Same as 'plain', this way we can use it in template
73 % This way we can use \pagestyle{normal} in LaTeX template
|
| A D | sphinxoptionsgeometry.sty | 30 % the way we found in order for the papersize special written by
|
| /trusted-firmware-a/docs/plat/ |
| A D | nvidia-tegra.rst | 34 implements a 7-way superscalar microarchitecture (up to 7 concurrent
35 micro-ops can be executed per clock), and includes a 128KB 4-way L1
36 instruction cache, a 64KB 4-way L1 data cache, and a 2MB 16-way L2
|
| A D | rpi4.rst | 31 arm64 Linux kernels are known to work this way.
66 To accommodate this existing way of configuring and setting up the board,
|
| A D | imx8m.rst | 53 When setting NEED_BL2=1 on imx8mm. We support an alternative way of
|
| A D | stm32mp1.rst | 42 The use of FIP is now the recommended way to boot STM32MP1 platform.
49 Although still supported, this way of booting is not recommended.
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/plat/ |
| A D | nvidia-tegra.rst.txt | 34 implements a 7-way superscalar microarchitecture (up to 7 concurrent
35 micro-ops can be executed per clock), and includes a 128KB 4-way L1
36 instruction cache, a 64KB 4-way L1 data cache, and a 2MB 16-way L2
|
| A D | rpi4.rst.txt | 31 arm64 Linux kernels are known to work this way.
66 To accommodate this existing way of configuring and setting up the board,
|
| A D | imx8m.rst.txt | 53 When setting NEED_BL2=1 on imx8mm. We support an alternative way of
|
| A D | stm32mp1.rst.txt | 42 The use of FIP is now the recommended way to boot STM32MP1 platform.
49 Although still supported, this way of booting is not recommended.
|
| /trusted-firmware-a/docs/design_documents/ |
| A D | cmake_framework.rst | 63 macros, etc. in a structured way. It contains two utilities for this purpose:
83 This provides a more granular way than the current Makefile system where most of
91 way it is not tied to one specific compiler.
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/design_documents/ |
| A D | cmake_framework.rst.txt | 63 macros, etc. in a structured way. It contains two utilities for this purpose:
83 This provides a more granular way than the current Makefile system where most of
91 way it is not tied to one specific compiler.
|
| /trusted-firmware-a/tools/nxp/create_pbl/ |
| A D | README | 13 Usage in standalone way:
|
| /trusted-firmware-a/docs/process/ |
| A D | code-review-guidelines.rst | 73 directory to have the freedom to change it in any way. This way, your changes
196 make it more flexible and fit slightly different use cases. That way, these
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/process/ |
| A D | code-review-guidelines.rst.txt | 73 directory to have the freedom to change it in any way. This way, your changes
196 make it more flexible and fit slightly different use cases. That way, these
|
| /trusted-firmware-a/docs/design/ |
| A D | psci-pd-tree.rst | 29 node at each level. The natural way to perform this traversal is to
34 a way which facilitates such a traversal.
41 Therefore, there is a need to implement the tree in a way which facilitates this
|
| A D | reset-design.rst | 119 the FVP models in this way.
134 same way.
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/design/ |
| A D | psci-pd-tree.rst.txt | 29 node at each level. The natural way to perform this traversal is to
34 a way which facilitates such a traversal.
41 Therefore, there is a need to implement the tree in a way which facilitates this
|
| A D | reset-design.rst.txt | 119 the FVP models in this way.
134 same way.
|
| /trusted-firmware-a/docs/components/ |
| A D | xlat-tables-lib-v2-design.rst | 62 An ``mmap_region`` is an abstract, concise way to represent a memory region to
246 of the MMU, the two are still related in some way. Static regions can only be
273 the new region will overlap another one in an invalid way, or if any other
339 The mmap regions list is a conceptual way to represent the memory layout. At
345 of the ``mmap_add*()`` APIs does not affect the translation tables in any way,
386 The mmap regions are sorted in a way that simplifies the code that maps
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/ |
| A D | xlat-tables-lib-v2-design.rst.txt | 62 An ``mmap_region`` is an abstract, concise way to represent a memory region to
246 of the MMU, the two are still related in some way. Static regions can only be
273 the new region will overlap another one in an invalid way, or if any other
339 The mmap regions list is a conceptual way to represent the memory layout. At
345 of the ``mmap_add*()`` APIs does not affect the translation tables in any way,
386 The mmap regions are sorted in a way that simplifies the code that maps
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/plat/arm/juno/ |
| A D | index.rst.txt | 192 In the same way, the address ns_bl2u_base_address is the value of
215 The Trusted Firmware must be compiled in a similar way as for FVP explained
|
| /trusted-firmware-a/docs/plat/arm/juno/ |
| A D | index.rst | 192 In the same way, the address ns_bl2u_base_address is the value of
215 The Trusted Firmware must be compiled in a similar way as for FVP explained
|