diff options
author | Ard Biesheuvel <ardb@kernel.org> | 2025-01-16 15:21:15 +0100 |
---|---|---|
committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2025-01-17 18:37:27 +0000 |
commit | 555bbc6643eaef7192f948391e5d16fae439a8c2 (patch) | |
tree | 116584c4d7b71de9213ec73cfa59d7ffd9960b22 /BaseTools/Source/Python | |
parent | ea2f6c68ee92677787604cf0a9f412edbc2e599f (diff) | |
download | edk2-555bbc6643eaef7192f948391e5d16fae439a8c2.zip edk2-555bbc6643eaef7192f948391e5d16fae439a8c2.tar.gz edk2-555bbc6643eaef7192f948391e5d16fae439a8c2.tar.bz2 |
ArmPkg/ArmGic: Drop GICv2 legacy support
Support for GICv2 legacy mode was introduced to accommodate secure world
firmware that was lagging behind in terms of development, and was
running the GIC in v2 mode on the secure side for lack of a GICv3
driver.
As per the GIC architecture, the non-secure world can only run the GIC
in v3 mode if the secure world does so too.
At this point, there is no longer a need to for this fallback: GICv2
support it still needed for platforms such as Raspberry Pi 4 that do not
implement GICv3 at all. But on platforms that do implement it, falling
back to GICv2 is unnecessary.
Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Diffstat (limited to 'BaseTools/Source/Python')
0 files changed, 0 insertions, 0 deletions