Prasad Kummari 889e3d1c68 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		2023-09-06 13:37:57 +02:00
..
aarch64	refactor(el3-runtime): move interrupt exception handler from macro to a function	2023-07-21 09:59:33 +01:00
bl31.ld.S	chore(bl): add UNALIGNED symbols for TEXT/RODATA	2023-06-12 12:50:08 +02:00
bl31.mk	refactor(pmu): convert FEAT_MTPMU to C and move to persistent register init	2023-06-29 09:59:06 +01:00
bl31_context_mgmt.c	feat(rme): add context management changes for FEAT_RME	2021-10-05 18:41:35 +02:00
bl31_main.c	fix(bl31): resolve runtime console garbage in next stage	2023-09-06 13:37:57 +02:00
bl31_traps.c	feat(el3-runtime): handle traps for IMPDEF registers accesses	2023-04-30 11:04:59 +01:00
ehf.c	fix(bl31): allow use of EHF with S-EL2 SPMC	2022-08-30 08:29:25 -07:00
interrupt_mgmt.c	Use correct type when reading SCR register	2020-01-28 11:10:48 +00:00