summaryrefslogtreecommitdiff
path: root/BaseTools/Source
diff options
context:
space:
mode:
authorPierre Gondois <Pierre.Gondois@arm.com>2021-12-09 10:31:57 +0100
committermergify[bot] <37929162+mergify[bot]@users.noreply.github.com>2021-12-14 16:07:00 +0000
commit8d2691c3d5cd13f118be50dca500f3049931b3d9 (patch)
tree9a01aeb5dcb71a7b69b39d0b4db8e4fe9f831f98 /BaseTools/Source
parent5d8b5d171c684ad2c820ee249c1bb86ce273cf68 (diff)
downloadedk2-8d2691c3d5cd13f118be50dca500f3049931b3d9.zip
edk2-8d2691c3d5cd13f118be50dca500f3049931b3d9.tar.gz
edk2-8d2691c3d5cd13f118be50dca500f3049931b3d9.tar.bz2
DynamicTablesPkg: FdtHwInfoParser: Add Boot Arch parser
The Fixed ACPI Description Table (FADT) is a mandatory table required for booting a standards-based operating system. The FADT table has an 'ARM Boot Architecture Flags' field that is used by an OS at boot time to determine the code path during boot. This field is used to specify if the platform complies with the PSCI specification. It is also used to describe the conduit (SMC/HVC) to be used for PSCI. The PSCI compliance information for a platform is described in the platform Device Tree, the bindings for which can be found at: - linux/Documentation/devicetree/bindings/arm/psci.yaml The FdtHwInfoParser implements a Boot Arch Parser that parses the platform Device Tree to create a CM_ARM_BOOT_ARCH_INFO object. The CM_ARM_BOOT_ARCH_INFO object is encapsulated in a Configuration Manager descriptor object and added to the platform information repository. The platform Configuration Manager can then utilise this information when generating the FADT table. Signed-off-by: Pierre Gondois <Pierre.Gondois@arm.com> Reviewed-by: Sami Mujawar <sami.mujawar@arm.com>
Diffstat (limited to 'BaseTools/Source')
0 files changed, 0 insertions, 0 deletions