Searched refs:stack (Results 1 – 25 of 28) sorted by relevance
12
| /trusted-firmware-a-3.4.0/fdts/ |
| D | juno-ethosn.dtsi | 9 * Arm Ethos-N NPU driver stack.
10 * https://github.com/ARM-software/ethos-n-driver-stack
|
| /trusted-firmware-a-3.4.0/lib/stack_protector/ |
| D | stack_protector.mk | 15 TF_CFLAGS += -fno-stack-protector
|
| /trusted-firmware-a-3.4.0/drivers/renesas/common/pwrc/ |
| D | pwrc.h | 74 extern uint32_t rcar_pwrc_switch_stack(uintptr_t jump, uintptr_t stack,
|
| D | pwrc.c | 733 uintptr_t stack = (uintptr_t) (DEVICE_SRAM_STACK_BASE + in rcar_pwrc_set_suspend_to_ram() local
744 rcar_pwrc_switch_stack(jump, stack, NULL); in rcar_pwrc_set_suspend_to_ram()
|
| /trusted-firmware-a-3.4.0/docs/plat/arm/juno/ |
| D | index.rst | 16 stack that includes TF-A. This version of TF-A is tested with pre-built
17 `Linaro release software stack`_ version 20.01. You can alternatively
18 build the software stack yourself by following the
19 `Juno platform software user guide`_. Once you prepare the software stack
28 a single FIP binary. It assumes that a Linaro release software stack has been
246 .. _Linaro release software stack: http://releases.linaro.org/members/arm/platforms/
|
| /trusted-firmware-a-3.4.0/lib/compiler-rt/builtins/ |
| D | assembly.h | 48 #define NO_EXEC_STACK_DIRECTIVE .section .note.GNU-stack,"",%progbits
|
| /trusted-firmware-a-3.4.0/docs/security_advisories/ |
| D | security-advisory-tfv-7.rst | 58 This approach permanently mitigates the entire software stack and no additional
87 approach will effectively permanently mitigate the entire software stack, since
|
| D | security-advisory-tfv-8.rst | 29 ``x0`` to ``x3`` are not part of the CPU context saved on the stack.
38 CPU context stored on the stack. This includes registers ``x0`` to ``x3``, as
|
| D | security-advisory-tfv-9.rst | 104 (from r1p0). The patch stack also includes an implementation for a specified
|
| /trusted-firmware-a-3.4.0/docs/plat/arm/fvp-ve/ |
| D | index.rst | 27 - Obtain arm toolchain. The software stack has been verified with linaro 6.2
|
| /trusted-firmware-a-3.4.0/services/spd/trusty/ |
| D | trusty.c | 172 uint64_t handler, uint64_t stack) in trusty_set_fiq_handler() argument
184 ctx->fiq_handler_sp = stack; in trusty_set_fiq_handler()
|
| /trusted-firmware-a-3.4.0/plat/renesas/common/ |
| D | plat_pm.c | 39 extern void rcar_pwrc_restore_generic_timer(uint64_t *stack);
|
| /trusted-firmware-a-3.4.0/docs/components/ |
| D | exception-handling.rst | 62 rest of the handling to a dedicated software stack running at lower Secure
66 processing of the error to dedicated software stack running at lower secure
95 priority levels as applicable for the Secure software stack. It then assigns the
132 stack—priority levels stack up in strictly increasing fashion, and need to be
|
| D | sdei.rst | 311 written in C: compilers typically adjust the stack frame at the beginning and
343 /* Save link register whilst maintaining stack alignment */
|
| D | secure-partition-manager-mm.rst | 33 The following diagram illustrates the corresponding software stack:
38 centres and enterprise servers) the secure software stack typically does not
72 Armv8-A software stack. A single or multiple Secure Partitions provide secure
477 A non-zero value will indicate that the SPM has initialised the stack pointer
|
| D | secure-partition-manager.rst | 126 Sample reference stack
181 stack.
182 - When ``SPMD_SPM_AT_SEL2=1``, the reference software stack assumes enablement
1240 Hafnium enables the compiler option permitting to leverage MTE stack tagging
|
| D | rmm-el3-comms-spec.rst | 370 #. General purpose registers (x0-x30) and ``sp_el0``, ``sp_el2`` stack pointers
|
| /trusted-firmware-a-3.4.0/docs/getting_started/ |
| D | porting-guide.rst | 41 each BL stage to correctly port the firmware stack. They are categorized as
117 Defines the normal stack memory available to each CPU. This constant is used
971 This function sets the current stack pointer to the normal memory stack that
973 stack for the primary CPU, the UP version of the function is used. The size
974 of the stack allocated to each CPU is specified by the platform defined
989 This function returns the base address of the normal memory stack that
991 stack for the primary CPU, the UP version of the function is used. The size
992 of the stack allocated to each CPU is specified by the platform defined
1055 it has restrictions for stack usage and it can use the registers x0 - x17 as
1134 when the stack protector is enabled with ENABLE_STACK_PROTECTOR. A predictable
[all …]
|
| D | psci-lib-integration-guide.rst | 163 - The C runtime environment must be setup and stack initialized
282 - Invalidates the stack and enables the data cache.
|
| D | build-options.rst | 435 - ``ENABLE_STACK_PROTECTOR``: String option to enable the stack protection
437 default value is set to "none". "strong" is the recommended stack protection
438 level if this feature is desired. "none" disables the stack protection. For
938 tagging for stack or not. It accepts 2 values: ``yes`` and ``no``. The
|
| /trusted-firmware-a-3.4.0/docs/plat/ |
| D | stm32mp1.rst | 271 - ``ENABLE_STACK_PROTECTOR``: To enable the stack protection.
|
| /trusted-firmware-a-3.4.0/docs/ |
| D | change-log.md | 833 …- change stack size of BL31 ([d544dfc](https://review.trustedfirmware.org/plugins/gitiles/TF-A/tru…
1354 …- enabling stack protector for diphda ([c7e4f1c](https://review.trustedfirmware.org/plugins/gitile…
1468 …- add a USB DFU stack ([efbd65f](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-f…
1642 …- add a USB device stack ([859bfd8](https://review.trustedfirmware.org/plugins/gitiles/TF-A/truste…
1731 …- bump BL2 stack size ([d22f1d3](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-f…
1798 …- do not keep mmc_device_info in stack ([99d37c8](https://review.trustedfirmware.org/plugins/gitil…
2330 - Added support for stack protector
2630 - Avoid duplicates in extension stack
2694 - Do not keep mmc_device_info in stack
2701 - Do not keep mmc_device_info in stack
[all …]
|
| /trusted-firmware-a-3.4.0/ |
| D | Makefile | 240 TF_CFLAGS += -mmemtag-stack
|
| /trusted-firmware-a-3.4.0/docs/design/ |
| D | firmware-design.rst | 252 bit. Alignment and stack alignment checking is enabled by setting the
994 framework finally sets up the execution stack for the handler, and invokes the
998 before restoring the stack and CPU state and returning from the original SMC.
1187 A dedicated per-CPU crash stack is maintained by BL31 and this is retrieved via
1482 C run time. Therefore it must follow AAPCS, and must not use stack.
1492 must follow AAPCS and may use stack.
|
| /trusted-firmware-a-3.4.0/docs/process/ |
| D | coding-guidelines.rst | 232 call stack.
|
12
