[edk2] [PATCH 0/2] ARM Dynamic Configuration

Chandni Cherukuri posted 2 patches 5 years, 11 months ago
Failed in applying to current master (apply log)
There is a newer version of this series
.../ARM/SgiPkg/Drivers/PlatformDxe/PlatformDxe.c   | 25 +++++-
.../ARM/SgiPkg/Drivers/PlatformDxe/PlatformDxe.inf |  2 +
Platform/ARM/SgiPkg/Include/SgiPlatform.h          | 18 +++++
.../SgiPkg/Library/PlatformLib/AArch64/Helper.S    |  7 ++
.../ARM/SgiPkg/Library/PlatformLib/PlatformLib.c   | 10 +++
.../ARM/SgiPkg/Library/PlatformLib/PlatformLib.inf |  3 +
.../Library/SgiPlatformPeiLib/SgiPlatformPeiLib.c  | 92 ++++++++++++++++++++++
.../SgiPlatformPeiLib/SgiPlatformPeiLib.inf        | 40 ++++++++++
Platform/ARM/SgiPkg/SgiPlatform.dec                |  5 ++
Platform/ARM/SgiPkg/SgiPlatform.dsc                |  1 +
Platform/ARM/SgiPkg/SgiPlatform.fdf                |  1 +
11 files changed, 203 insertions(+), 1 deletion(-)
create mode 100644 Platform/ARM/SgiPkg/Library/SgiPlatformPeiLib/SgiPlatformPeiLib.c
create mode 100644 Platform/ARM/SgiPkg/Library/SgiPlatformPeiLib/SgiPlatformPeiLib.inf
[edk2] [PATCH 0/2] ARM Dynamic Configuration
Posted by Chandni Cherukuri 5 years, 11 months ago
On SGI platforms, the trusted firmware executes prior to the SEC
phase. It supplies to the SEC phase a pointer to a HW CONFIG fdt
in the x1 which contains platform specific information such as part
number and config number of the SGI platform. 

The HW CONFIG FDT would look as,
/dts-v1/;
/ {
        /* compatible string */
        compatible = "arm,sgi-isys3";

	/* platform ID node */
	system-id {
	     platform-id = <0x03000783>;
	}
};

In the very first step of the assembly code which executes in SEC phase
the fdt pointer is stored in a global variable from the register. A PPI 
is created during the SEC phase which stores the global variable.

During PEI phase, a Platform ID PEIM is installed which accessess the PPI
and retrieves the platform information using FDT helper functions and a
PlatformId HOB is created and populated with the information.
 
During DXE phase the drivers can access the Platform ID HOB to get the
platform information and perform platform specific functions based on the
platform.

Chandni Cherukuri (2):
  Platform/ARM/Sgi: Install a Platform ID HOB
  Platform/ARM/Sgi: Pick ACPI tables to install based on platform ID

 .../ARM/SgiPkg/Drivers/PlatformDxe/PlatformDxe.c   | 25 +++++-
 .../ARM/SgiPkg/Drivers/PlatformDxe/PlatformDxe.inf |  2 +
 Platform/ARM/SgiPkg/Include/SgiPlatform.h          | 18 +++++
 .../SgiPkg/Library/PlatformLib/AArch64/Helper.S    |  7 ++
 .../ARM/SgiPkg/Library/PlatformLib/PlatformLib.c   | 10 +++
 .../ARM/SgiPkg/Library/PlatformLib/PlatformLib.inf |  3 +
 .../Library/SgiPlatformPeiLib/SgiPlatformPeiLib.c  | 92 ++++++++++++++++++++++
 .../SgiPlatformPeiLib/SgiPlatformPeiLib.inf        | 40 ++++++++++
 Platform/ARM/SgiPkg/SgiPlatform.dec                |  5 ++
 Platform/ARM/SgiPkg/SgiPlatform.dsc                |  1 +
 Platform/ARM/SgiPkg/SgiPlatform.fdf                |  1 +
 11 files changed, 203 insertions(+), 1 deletion(-)
 create mode 100644 Platform/ARM/SgiPkg/Library/SgiPlatformPeiLib/SgiPlatformPeiLib.c
 create mode 100644 Platform/ARM/SgiPkg/Library/SgiPlatformPeiLib/SgiPlatformPeiLib.inf

-- 
2.7.4

_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel