diff options
| author | Ard Biesheuvel <ardb@kernel.org> | 2025-01-29 11:29:54 +0100 |
|---|---|---|
| committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2025-01-30 13:07:05 +0000 |
| commit | afdae789cd0d33c6f7debce2fc41f1af4946d869 (patch) | |
| tree | d08b7ad217b62c4351e18dcfc26a7d03647502ee /BaseTools/Source/Python/FirmwareStorageFormat/FfsFileHeader.py | |
| parent | b64f735867ead2e1b4cc2df5d1ee8a4273ee7c39 (diff) | |
| download | edk2-afdae789cd0d33c6f7debce2fc41f1af4946d869.tar.gz edk2-afdae789cd0d33c6f7debce2fc41f1af4946d869.tar.bz2 edk2-afdae789cd0d33c6f7debce2fc41f1af4946d869.zip | |
ArmPkg/CpuDxe: Fix error handling in driver initialization
Failure to install the CPU arch protocol is a fatal error, so treat it
as such, rather than ignore it, even though we won't get very far if
this driver fails to dispatch - at least, we will get an error in a
DEBUG build rather than a mysterious failure due to unsatisfied DEPEXes.
Failure to install the idle loop event handler is not a fatal error, and
it should not cause the driver to exit with an error, as this will
unload the driver and keep the installed CPU arch protocol pointer
dangling. So keep the ASSERT() on the return value, but return
EFI_SUCCESS once we're past the point where the CPU arch protocol has
been installed.
Since the protocol is never uninstalled, make the CPU handle function
local, as there is no point in keeping its value around.
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Diffstat (limited to 'BaseTools/Source/Python/FirmwareStorageFormat/FfsFileHeader.py')
0 files changed, 0 insertions, 0 deletions