Searched hist:"2948 d1f81904f02034a0d12faf9b8c7f34b05795" (Results 1 – 2 of 2) sorted by relevance
| /rk3399_ARM-atf/plat/arm/common/ |
| H A D | arm_bl1_setup.c | 2948d1f81904f02034a0d12faf9b8c7f34b05795 Mon Dec 23 16:18:58 UTC 2024 Harrison Mutai <harrison.mutai@arm.com> fix(arm): reinit secure and non-secure tls
Initializing the transfer list using `transfer_list_ensure` allows reuse
of an already initialized transfer list. While this is beneficial when
receiving a transfer list and ensuring one exists, it causes issues
during a system RESET if the old content of SRAM is not cleared.
To prevent this, at least one step in the reset path must zero intialise
the transfer list memory. Unless a previous stage explicitly provides a
transfer list via boot arguments, a fresh transfer list should be
created.
This change ensures that BL1 and BL31 properly reinitialize the transfer
lists, preserving correctness for secure and non-secure handoffs in
TF-A.
Change-Id: I3bfaa9e76df932a637031d645e4a22d857a094a5
Signed-off-by: Harrison Mutai <harrison.mutai@arm.com>
|
| H A D | arm_bl31_setup.c | 2948d1f81904f02034a0d12faf9b8c7f34b05795 Mon Dec 23 16:18:58 UTC 2024 Harrison Mutai <harrison.mutai@arm.com> fix(arm): reinit secure and non-secure tls
Initializing the transfer list using `transfer_list_ensure` allows reuse
of an already initialized transfer list. While this is beneficial when
receiving a transfer list and ensuring one exists, it causes issues
during a system RESET if the old content of SRAM is not cleared.
To prevent this, at least one step in the reset path must zero intialise
the transfer list memory. Unless a previous stage explicitly provides a
transfer list via boot arguments, a fresh transfer list should be
created.
This change ensures that BL1 and BL31 properly reinitialize the transfer
lists, preserving correctness for secure and non-secure handoffs in
TF-A.
Change-Id: I3bfaa9e76df932a637031d645e4a22d857a094a5
Signed-off-by: Harrison Mutai <harrison.mutai@arm.com>
|