fix(bl31): resolve runtime console garbage in next stage

When BL31 software is sending data through a communication channel,
there's a chance that the final portion of the data could become
disrupted, if another software (BL32/RMM) starts setting up the
channel at the same time. To solve this issue, make sure to flush the
console data from BL31, before initializing BL32/RMM. This makes sure
that the communication stays reliable.

Signed-off-by: Prasad Kummari <prasad.kummari@amd.com>
Change-Id: Icb8003e068b0b93bc4672e05f69001d9694a175c
This commit is contained in:
Prasad Kummari 2023-08-14 11:55:50 +05:30 committed by Kummari Prasad
parent e27bebb0fe
commit 889e3d1c68

View file

@ -163,6 +163,7 @@ void bl31_main(void)
if (bl32_init != NULL) {
INFO("BL31: Initializing BL32\n");
console_flush();
int32_t rc = (*bl32_init)();
if (rc == 0) {
@ -178,6 +179,7 @@ void bl31_main(void)
if (rmm_init != NULL) {
INFO("BL31: Initializing RMM\n");
console_flush();
int32_t rc = (*rmm_init)();
if (rc == 0) {