/** @file\r
PI PEI master include file. This file should match the PI spec.\r
\r
-Copyright (c) 2006 - 2013, Intel Corporation. All rights reserved.<BR>\r
+Copyright (c) 2006 - 2017, Intel Corporation. All rights reserved.<BR>\r
This program and the accompanying materials are licensed and made available under \r
the terms and conditions of the BSD License that accompanies this distribution. \r
The full text of the license may be found at\r
WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED. \r
\r
@par Revision Reference:\r
- PI Version 1.2.\r
+ PI Version 1.4a.\r
\r
**/\r
\r
@param Ppi Address of the PPI that was installed.\r
\r
@return Status of the notification.\r
+ The status code returned from this function is ignored.\r
**/\r
typedef\r
EFI_STATUS\r
\r
@retval EFI_SUCCESS The interface was successfully installed.\r
@retval EFI_INVALID_PARAMETER The PpiList pointer is NULL, or any of the PEI PPI descriptors in the \r
- list do not have the EFI_PEI_PPI_DESCRIPTOR_PPI bit set in the Flags field.\r
+ list do not have the EFI_PEI_PPI_DESCRIPTOR_NOTIFY_TYPES bit set in the Flags field.\r
@retval EFI_OUT_OF_RESOURCES There is no additional space in the PPI database.\r
\r
**/\r
The purpose of the service is to publish an interface that allows \r
PEIMs to allocate memory ranges that are managed by the PEI Foundation.\r
\r
+ Prior to InstallPeiMemory() being called, PEI will allocate pages from the heap.\r
+ After InstallPeiMemory() is called, PEI will allocate pages within the region\r
+ of memory provided by InstallPeiMemory() service in a best-effort fashion.\r
+ Location-specific allocations are not managed by the PEI foundation code.\r
+\r
@param PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.\r
@param MemoryType The type of memory to allocate.\r
@param Pages The number of contiguous 4 KB pages to allocate.\r
@retval EFI_OUT_OF_RESOURCES The pages could not be allocated.\r
@retval EFI_INVALID_PARAMETER The type is not equal to EfiLoaderCode, EfiLoaderData, EfiRuntimeServicesCode, \r
EfiRuntimeServicesData, EfiBootServicesCode, EfiBootServicesData,\r
- EfiACPIReclaimMemory, or EfiACPIMemoryNVS.\r
+ EfiACPIReclaimMemory, EfiReservedMemoryType, or EfiACPIMemoryNVS.\r
\r
**/\r
typedef\r
OUT EFI_PHYSICAL_ADDRESS *Memory\r
);\r
\r
+/**\r
+ Frees memory pages.\r
+\r
+ @param[in] PeiServices An indirect pointer to the EFI_PEI_SERVICES table published by the PEI Foundation.\r
+ @param[in] Memory The base physical address of the pages to be freed.\r
+ @param[in] Pages The number of contiguous 4 KB pages to free.\r
+\r
+ @retval EFI_SUCCESS The requested pages were freed.\r
+ @retval EFI_INVALID_PARAMETER Memory is not a page-aligned address or Pages is invalid.\r
+ @retval EFI_NOT_FOUND The requested memory pages were not allocated with\r
+ AllocatePages().\r
+\r
+**/\r
+typedef\r
+EFI_STATUS\r
+(EFIAPI *EFI_PEI_FREE_PAGES) (\r
+ IN CONST EFI_PEI_SERVICES **PeiServices,\r
+ IN EFI_PHYSICAL_ADDRESS Memory,\r
+ IN UINTN Pages\r
+ );\r
+\r
/**\r
The purpose of this service is to publish an interface that \r
allows PEIMs to allocate memory ranges that are managed by the PEI Foundation.\r
IN CONST EFI_PEI_SERVICES **PeiServices\r
);\r
\r
+/**\r
+ Resets the entire platform.\r
+\r
+ @param[in] ResetType The type of reset to perform.\r
+ @param[in] ResetStatus The status code for the reset.\r
+ @param[in] DataSize The size, in bytes, of ResetData.\r
+ @param[in] ResetData For a ResetType of EfiResetCold, EfiResetWarm, or EfiResetShutdown\r
+ the data buffer starts with a Null-terminated string, optionally\r
+ followed by additional binary data. The string is a description\r
+ that the caller may use to further indicate the reason for the\r
+ system reset. ResetData is only valid if ResetStatus is something\r
+ other than EFI_SUCCESS unless the ResetType is EfiResetPlatformSpecific\r
+ where a minimum amount of ResetData is always required.\r
+\r
+**/\r
+typedef\r
+VOID\r
+(EFIAPI *EFI_PEI_RESET2_SYSTEM) (\r
+ IN EFI_RESET_TYPE ResetType,\r
+ IN EFI_STATUS ResetStatus,\r
+ IN UINTN DataSize,\r
+ IN VOID *ResetData OPTIONAL\r
+ );\r
+\r
/**\r
Find a file within a volume by its name.\r
\r
// PEI Specification Revision information\r
//\r
#define PEI_SPECIFICATION_MAJOR_REVISION 1\r
-#define PEI_SPECIFICATION_MINOR_REVISION 20\r
+#define PEI_SPECIFICATION_MINOR_REVISION 40\r
///\r
/// Specification inconsistency here: \r
/// In the PI1.0 spec, PEI_SERVICES_SIGNATURE is defined as 0x5652455320494550. But \r
EFI_PEI_REGISTER_FOR_SHADOW RegisterForShadow;\r
EFI_PEI_FFS_FIND_SECTION_DATA3 FindSectionData3;\r
EFI_PEI_FFS_GET_FILE_INFO2 FfsGetFileInfo2;\r
+ EFI_PEI_RESET2_SYSTEM ResetSystem2;\r
+ EFI_PEI_FREE_PAGES FreePages;\r
};\r
\r
\r
allows the SEC phase to pass information about the stack,\r
temporary RAM and the Boot Firmware Volume. In addition, it also\r
allows the SEC phase to pass services and data forward for use\r
- during the PEI phase in the form of one or more PPIs. There is\r
- no limit to the number of additional PPIs that can be passed\r
- from SEC into the PEI Foundation. As part of its initialization\r
- phase, the PEI Foundation will add these SEC-hosted PPIs to its\r
- PPI database such that both the PEI Foundation and any modules\r
- can leverage the associated service calls and/or code in these\r
- early PPIs.\r
+ during the PEI phase in the form of one or more PPIs. These PPI's\r
+ will be installed and/or immediately signaled if they are\r
+ notification type. There is no limit to the number of additional\r
+ PPIs that can be passed from SEC into the PEI Foundation. As part\r
+ of its initialization phase, the PEI Foundation will add these\r
+ SEC-hosted PPIs to its PPI database such that both the PEI\r
+ Foundation and any modules can leverage the associated service\r
+ calls and/or code in these early PPIs.\r
\r
@param SecCoreData Points to a data structure containing\r
information about the PEI core's\r
projects / mirror_edk2.git / blobdiff