Fix issue broken doxygen parsing. The issue is that when declaring a function pointer type, the "(" for parameter should follows ")" of function type name without any blank, for example:

Bad: "typedef EFI_STATUS (EFIAPI name) (parameter list)"
GOOD: "typedef EFI_STATUS (EFIAPI name)(parameter list)"

git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@5362 6f19259b-4bc3-4df7-8a09-765794883524
This commit is contained in:
klu2 2008-06-24 04:01:35 +00:00
parent 813acf3a9a
commit 6de794cd4a
1 changed files with 64 additions and 37 deletions

View File

@ -1,4 +1,3 @@
/** @file
PI PEI master include file. This file should match the PI spec.
@ -21,16 +20,24 @@
#include <Pi/PiMultiPhase.h>
//
// Handles of EFI FV/FFS.
//
///
/// Handles of EFI FV.
///
typedef VOID *EFI_PEI_FV_HANDLE;
///
/// Handles of EFI FFS
///
typedef VOID *EFI_PEI_FILE_HANDLE;
//
// Declare forward referenced data structures
//
///
/// Declare forward reference data structure for EFI_PEI_SERVICE
///
typedef struct _EFI_PEI_SERVICES EFI_PEI_SERVICES;
///
/// Declare forward reference data structure for EFI_PEI_NOTIFY_DESCRIPTOR
///
typedef struct _EFI_PEI_NOTIFY_DESCRIPTOR EFI_PEI_NOTIFY_DESCRIPTOR;
@ -42,7 +49,7 @@ typedef struct _EFI_PEI_NOTIFY_DESCRIPTOR EFI_PEI_NOTIFY_DESCRIPTOR;
The PEI Dispatcher will invoke each PEIM one time. During this pass, the PEI
Dispatcher will pass control to the PEIM at the AddressOfEntryPoint in the PE Header.
@param FfsHeader Pointer to the FFS file header.
@param FileHandle Pointer to the FFS file header.
@param PeiServices Describes the list of possible PEI Services.
@return Status code
@ -63,7 +70,6 @@ EFI_STATUS
@param Ppi Address of the PPI that was installed.
@return Status code
**/
typedef
EFI_STATUS
@ -83,23 +89,30 @@ EFI_STATUS
#define EFI_PEI_PPI_DESCRIPTOR_NOTIFY_TYPES 0x00000060
#define EFI_PEI_PPI_DESCRIPTOR_TERMINATE_LIST 0x80000000
///
/// The data structure through which a PEIM describes available services to the PEI Foundation.
///
typedef struct {
UINTN Flags;
EFI_GUID *Guid;
VOID *Ppi;
} EFI_PEI_PPI_DESCRIPTOR;
///
/// The data structure in a given PEIM that tells the PEI
/// Foundation where to invoke the notification service.
///
struct _EFI_PEI_NOTIFY_DESCRIPTOR {
UINTN Flags;
EFI_GUID *Guid;
EFI_PEIM_NOTIFY_ENTRY_POINT Notify;
};
//
// Describes request of the module to be loaded to
// the permanent memory once it is available. Unlike most of the other HOBs,
// this HOB is produced and consumed during the HOB producer phase.
//
///
/// Describes request of the module to be loaded to
/// the permanent memory once it is available. Unlike most of the other HOBs,
/// this HOB is produced and consumed during the HOB producer phase.
///
typedef struct _EFI_HOB_LOAD_PEIM {
EFI_HOB_GENERIC_HEADER Header;
EFI_PEI_FILE_HANDLE FileHandle;
@ -684,6 +697,15 @@ EFI_STATUS
#define PEI_SERVICES_SIGNATURE 0x5652455320494550ULL
#define PEI_SERVICES_REVISION ((PEI_SPECIFICATION_MAJOR_REVISION<<16) | (PEI_SPECIFICATION_MINOR_REVISION))
///
/// EFI_PEI_SERVICES is a collection of functions whose implementation is provided by the PEI
/// Foundation. These services fall into various classes, including the following:
/// - Managing the boot mode
/// - Allocating both early and permanent memory
/// - Supporting the Firmware File System (FFS)
/// - Abstracting the PPI database abstraction
/// - Creating Hand-Off Blocks (HOBs)
///
struct _EFI_PEI_SERVICES {
EFI_TABLE_HEADER Hdr;
//
@ -740,6 +762,11 @@ struct _EFI_PEI_SERVICES {
};
///
/// EFI_SEC_PEI_HAND_OFF structure hold information about
/// PEI core's operating environment, such as the size of location of
/// temporary RAM, the stack location and BFV location.
///
typedef struct _EFI_SEC_PEI_HAND_OFF {
//
// Size of the data structure.