diff options
| author | Ard Biesheuvel <ardb@kernel.org> | 2025-01-28 17:15:11 +0100 |
|---|---|---|
| committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2025-01-30 13:07:05 +0000 |
| commit | c558a3b18b45348670e00bc3e7644d39c701fce3 (patch) | |
| tree | 2b8d34dae35b6c772222c5298966ec8b29feb37e /BaseTools/Source/Python/FirmwareStorageFormat | |
| parent | 3c4c7a0fc98552a7a3f7866f06a49b2b4b8fa565 (diff) | |
| download | edk2-c558a3b18b45348670e00bc3e7644d39c701fce3.tar.gz edk2-c558a3b18b45348670e00bc3e7644d39c701fce3.tar.bz2 edk2-c558a3b18b45348670e00bc3e7644d39c701fce3.zip | |
ArmPkg/ArmGicDxe: Map GIC MMIO regions before use
The GIC driver itself has intimate knowledge of the hardware, and so it
is the best suited to create the mappings of the MMIO control regions,
in case they have not been mapped yet by the platform code.
So call in the the CPU arch protocol to map the CPU interface,
distributor and redistributor regions as they are discovered by the GIC
driver startup code.
Note that creating these mappings has no effect if the regions in
question have already been mapped with the correct attributes.
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Diffstat (limited to 'BaseTools/Source/Python/FirmwareStorageFormat')
0 files changed, 0 insertions, 0 deletions