[mirror_edk2.git] / MdeModulePkg / Universal / PCD / Pei / Pcd.inf

## @file\r
# PCD PEIM produces PCD database to manage all dynamic PCD in PEI phase and install Pcd Ppi service.\r
#\r
# This version PCD PEIM depends on the external PCD database binary file, not built in PCD data base.\r
# There are two PCD PPIs as follows:\r
#   1) PCD_PPI\r
#      It is EDKII implementation which support Dynamic/DynamicEx Pcds.\r
#   2) EFI_PEI_PCD_PPI\r
#      It is defined by PI specification 1.2, Vol 3 which only support dynamicEx\r
#      type Pcd.\r
# For dynamicEx type PCD, it is compatible between PCD_PPI and EFI_PEI_PCD_PPI.\r
# PCD PEIM driver will produce above two PPIs at same time.\r
#\r
# PCD database is generated as the separate binary image at build time. The binary image\r
# will be intergrated into Firmware volume together with PCD driver.\r
#\r
# ////////////////////////////////////////////////////////////////////////////////\r
# //                                                                            //\r
# //                      Introduction of PCD database                          //\r
# //                                                                            //\r
# ////////////////////////////////////////////////////////////////////////////////\r
#\r
# 1, Introduction\r
#    PCD database hold all dynamic type PCD information. The structure of PEI PCD\r
#    database is generated by build tools according to dynamic PCD usage for\r
#    specified platform.\r
#\r
# 2, Dynamic Type PCD\r
#    Dynamic type PCD is used for the configuration/setting which value is determined\r
#    dynamic. In contrast, the value of static type PCD (FeatureFlag, FixedPcd,\r
#    PatchablePcd) is fixed in final generated FD image in build time.\r
#\r
#    2.1 The "dynamic" determination means one of below cases:\r
#      a) The PCD setting value is produced by someone driver and consumed by\r
#         other driver in execution time.\r
#      b) The PCD setting value is set/get by user from FrontPage.\r
#      c) The PCD setting value is produced by platform OEM vendor in specified area.\r
#\r
#    2.2 According to module distribution way, dynamic PCD could be classfied as:\r
#      a) Dynamic:\r
#         If module is released in source code and will be built with platform\r
#         DSC, the dynamic PCD used by this module can be accessed as:\r
#                 PcdGetxx(PcdSampleDynamicPcd);\r
#         In building platform, build tools will translate PcdSampleDynamicPcd to\r
#         pair of {Token Space Guid: Token Number} for this PCD.\r
#      b) DynamicEx:\r
#         If module is release as binary and will not pariticpate platform building,\r
#         the dynamic PCD used by this module need be accessed as:\r
#               PcdGetxxEx(gEfiMyTokenspaceGuid, PcdSampleDynamicPcd)\r
#         Developer need explicity gives {Token Space Guid:Token Number} as parameter\r
#         in writting source code.\r
#\r
#    2.3 According to PCD value's storage method, dynamic PCD could be classfied as:\r
#      a) Default Storage:\r
#         - The PCD value is stored in PCD database maintained by PCD driver in boot\r
#           time memory.\r
#         - This type is used for communication between PEIM/DXE driver, DXE/DXE\r
#           driver. But all set/get value will be losted after boot-time memory\r
#           is turn off.\r
#         - [PcdsDynamicDefault] is used as section name for this type PCD in\r
#           platform DSC file. [PcdsDynamicExDefault] is used for dynamicEx type PCD.\r
#\r
#      b) Variable Storage:\r
#         - The PCD value is stored in variable area.\r
#         - As default storage type, this type PCD could be used for PEI/DXE driver\r
#           communication. But beside it, this type PCD could also be used to store\r
#           the value associate with a HII setting via variable interface.\r
#         - In PEI phase, the PCD value could only be got but can not be set due\r
#           to variable area is readonly.\r
#         - [PcdsDynamicHii] is used as section name for this type PCD in platform\r
#           DSC file. [PcdsDynamicExHii] is for dynamicEx type PCD.\r
#\r
#      c) OEM specificed storage area:\r
#         - The PCD value is stored in OEM specified area which base address is\r
#           specified by PCD setting - PcdVpdBaseAddress64 or PcdVpdBaseAddress.\r
#         - The area is read only for PEI and DXE phase.\r
#         - [PcdsDynamicVpd] is used as section name for this type PCD in platform\r
#           DSC file. [PcdsDynamicExVpd] is for dynamicex type PCD.\r
#\r
#    2.4 When and how to use dynamic PCD\r
#      Module developer do not care the used PCD is dynamic or static when writting\r
#      source code/INF. Dynamic PCD and dynamic type is pointed by platform integrator\r
#      in platform DSC file. Please ref section 2.3 to get matching between dynamic\r
#      PCD type and section name in DSC file.\r
#\r
# 3, PCD database:\r
#    Although dynamic PCD could be in different storage type as above description,\r
#    but the basic information and default value for all dynamic PCD is hold\r
#    by PCD database maintained by PEI/DXE driver.\r
#\r
#    As the whole EFI BIOS boot path is divided into PEI/DXE phase, the PCD database\r
#    also is divided into Pei/Dxe database maintaied by PcdPeim/PcdDxe driver separatly.\r
#    To make PcdPeim's driver image smaller, PEI PCD database only hold all dynamic\r
#    PCD information used in PEI phase or use in both PEI/DXE phase. And DXE PCD\r
#    database contains all PCDs used in PEI/DXE phase in memory.\r
#\r
#    Build tool will generate PCD database into the separate binary file for\r
#    PEI/DXE PCD driver according to dynamic PCD section in platform DSC file.\r
#\r
#    3.1 PcdPeim and PcdDxe\r
#      PEI PCD database is maintained by PcdPeim driver run from flash. PcdPeim driver\r
#      build guid hob in temporary memory and copy the binary data base from flash\r
#      to temporary memory for PEI PCD database.\r
#      DXE PCD database is maintained by PcdDxe driver.At entry point of PcdDxe driver,\r
#      a new PCD database is allocated in boot-time memory which including all\r
#      PEI PCD and DXE PCD entry.\r
#\r
#      Pcd driver should run as early as possible before any other driver access\r
#      dynamic PCD's value. PEI/DXE "Apriori File" mechanism make it possible by\r
#      making PcdPeim/PcdDxe as first dispatching driver in PEI/DXE phase.\r
#\r
#    3.2 Token space Guid/Token number, Platform token, Local token number\r
#           Dynamic PCD\r
#          +-----------+               +---------+\r
#          |TokenSpace |               |Platform |\r
#          |   Guid    |  build tool   | Token   |\r
#          |    +      +-------------->| Number  |\r
#          |  Token    |               +---------+`._\r
#          |  Number   |                             `.\r
#          +-----------+                               `.  +------+\r
#                                                        `-|Local |\r
#                                                          |Token |\r
#                               DynamicEx PCD            ,-|Number|\r
#                               +-----------+         ,-'  +------+\r
#                               |TokenSpace |      ,-'\r
#                               |   Guid    |  _,-'\r
#                               |    +      +.'\r
#                               |  Token    |\r
#                               |  Number   |\r
#                               +-----------+\r
#\r
#\r
#      3.2.1 Pair of Token space guid + Token number\r
#        Any type PCD is identified by pair of "TokenSpaceGuid + TokeNumber". But it\r
#        is not easy maintained by PCD driver, and hashed token number will make\r
#        searching slowly.\r
#\r
#      3.2.2 Platform Token Number\r
#        "Platform token number" concept is introduced for mapping to a pair of\r
#        "TokenSpaceGuid + TokenNumber". The platform token number is generated by\r
#        build tool in autogen.h and all of them are continual in a platform scope\r
#        started from 1.(0 meaning invalid internal token number)\r
#        With auto-generated "platform token number", PcdGet(PcdSampleDynamicPcd)\r
#        in source code is translated to LibPcdGet(_PCD_TOKEN_PcdSampleDynamicPcd)\r
#        in autogen.h.\r
#        Notes: The mapping between pair of "tokenspace guid + token number" and\r
#        "internal token number" need build tool establish, so "platform token number"\r
#        mechanism is not suitable for binary module which use DynamicEx type PCD.\r
#        To access a dynamicEx type PCD, pair of "token space guid/token number" all need\r
#        to be specificed for PcdSet/PcdGet accessing macro.\r
#\r
#        Platform Token Number is started from 1, and inceased continuous. From whole\r
#        platform scope, there are two zones: PEI Zone and DXE Zone\r
#                  |                      Platform Token Number\r
#        ----------|----------------------------------------------------------------\r
#        PEI Zone: |            1                 ~  PEI_LOCAL_TOKEN_NUMBER\r
#        DXE Zone: | (PEI_LOCAL_TOKEN_NUMBER + 1) ~ (PEI_LOCAL_TOKEN_NUMBER + DXE_LOCAL_TOKEN_NUMBER)\r
#\r
#      3.2.3 Local Token Number\r
#        To fast searching a PCD entry in PCD database, PCD driver translate\r
#        platform token number to local token number via a mapping table.\r
#        For binary DynamicEx type PCD, there is a another mapping table to translate\r
#        "token space guid + token number" to local token number directly.\r
#        Local token number is identifier for all internal interface in PCD PEI/DXE\r
#        driver.\r
#\r
#        A local token number is a 32-bit value in following meaning:\r
#         32 ------------- 28 ---------- 24 -------- 0\r
#          | PCD type mask  | Datum Type  |  Offset  |\r
#          +-----------------------------------------+\r
#        where:\r
#          PCd type mask: indicate Pcd type from following macro:\r
#                         PCD_TYPE_DATA\r
#                         PCD_TYPE_HII\r
#                         PCD_TYPE_VPD\r
#                         PCD_TYPE_STRING\r
#          Datum Type   : indicate PCD vaue type from following macro:\r
#                         PCD_DATUM_TYPE_POINTER\r
#                         PCD_DATUM_TYPE_UINT8\r
#                         PCD_DATUM_TYPE_UINT16\r
#                         PCD_DATUM_TYPE_UINT32\r
#                         PCD_DATUM_TYPE_UINT64\r
#          Offset      : indicate the related offset of PCD value in PCD database array.\r
#       Based on local token number, PCD driver could fast determine PCD type, value\r
#       type and get PCD entry from PCD database.\r
#\r
#    3.3 PCD Database binary file\r
#      PCD Database binary file will be created at build time as the standalone binary image.\r
#      To understand the binary image layout, PCD Database C structure is still generated\r
#      as comments by build tools in PCD driver's autogen.h/\r
#      autogen.c file. In generated C structure, following information is stored:\r
#      - ExMapTable: This table is used translate a binary dynamicex type PCD's\r
#                    "tokenguid + token" to local token number.\r
#      - LocalTokenNumberTable:\r
#                    This table stores all local token number in array, use "Internal\r
#                    token number" as array index to get PCD entry's offset fastly.\r
#      - SizeTable:  This table stores the size information for all PCD entry.\r
#      - GuidTable:  This table stores guid value for DynamicEx's token space,\r
#                    HII type PCD's variable GUID.\r
#      - SkuIdTable: TBD\r
#      - SystemSkuId: TBD\r
#      - PCD value structure:\r
#                    Every PCD has a value record in PCD database. For different\r
#                    datum type PCD has different record structure which will be\r
#                    introduced in 3.3.1\r
#\r
#      In a PCD database structure, there are two major area: Init and UnInit.\r
#      Init area is use stored above PCD internal structure such as ExMapTable,\r
#      LocalTokenNumberTable etc and the (default) value of PCD which has default\r
#      value specified in platform DSC file.\r
#      Unint area is used stored the value of PCD which has no default value in\r
#      platform DSC file, the value of NULL, 0 specified in platform DSC file can\r
#      be seemed as "no default value".\r
#\r
#      3.3.1 Simple Sample PCD Database C Structure\r
#        A general sample of PCD database structue is as follows:\r
#        typedef struct _PCD_DATABASE {\r
#          typedef struct _PCD_DATABASE_INIT {\r
#            //===== Following is PCD database internal maintain structures\r
#            DYNAMICEX_MAPPING ExMapTable[PEI_EXMAPPING_TABLE_SIZE];\r
#            UINT32            LocalTokenNumberTable[PEI_LOCAL_TOKEN_NUMBER_TABLE_SIZE];\r
#            GUID              GuidTable[PEI_GUID_TABLE_SIZE];\r
#            SIZE_INFO         SizeTable[PEI_SIZE_TABLE_SIZE];\r
#            UINT8             SkuIdTable[PEI_SKUID_TABLE_SIZE];\r
#            SKU_ID            SystemSkuId;\r
#\r
#            //===== Following is value structure for PCD with default value\r
#            ....\r
#            ....\r
#            ....\r
#          } Init;\r
#          typedef struct _PCD_DATABSE_UNINIT {\r
#            //==== Following is value structure for PCD without default value\r
#            ....\r
#            ....\r
#          } UnInit;\r
#        }\r
#\r
#      3.3.2 PCD value structure in PCD database C structure\r
#        The value's structure is generated by build tool in PCD database C structure.\r
#        The PCDs in different datum type has different value structure.\r
#\r
#        3.3.2.1 UINT8/UINT16/UINT32/UINT64 datum type PCD\r
#          The C structure for these datum type PCD is just a UINT8/UINT16/UINT32/UINT64\r
#          data member in PCD database, For example:\r
#          UINT16  PcdHardwareErrorRecordLevel_d3705011_bc19_4af7_be16_f68030378c15_VariableDefault_0;\r
#          Above structure is generated by build tool, the member name is "PcdCName_Guidvalue"\r
#          Member type is UINT16 according to PcdHardwareErrorRecordLevel declaration\r
#          in DEC file.\r
#\r
#        3.3.2.2 VOID* datum type PCD\r
#          The value of VOID* datum type PCD is a UINT8/UINT16 array in PCD database.\r
#\r
#          3.3.2.2.1 VOID* - string type\r
#            If the default value for VOID* datum type PCD like L"xxx", the PCD is\r
#            used for unicode string, and C structure of this datum type PCD is\r
#            UINT16 string array in PCD database, for example:\r
#            UINT16 StringTable[29];\r
#            The number of 29 in above sample is max size of a unicode string.\r
#\r
#            If the default value for VOID* datum type PCD like "xxx", the PCD is\r
#            used for ascii string, and C structure of this datum type PCD is\r
#            UINT8 string array in PCD database, for example:\r
#            UINT8 StringTable[20];\r
#            The number of 20 in above sample is max size of a ascii string.\r
#\r
#          3.3.2.2.2 VOID* - byte array\r
#            If the default value of VOID* datum type PCD like {'0x29', '0x01', '0xf2'}\r
#            the PCD is used for byte array. The generated structrue is same as\r
#            above ascii string table,\r
#            UINT8 StringTable[13];\r
#            The number of 13 in above sample is max size of byte array.\r
#\r
#      3.3.3 Some utility structures in PCD Database\r
#        3.3.3.1 GuidTable\r
#          GuidTable array is used to store all related GUID value in PCD database:\r
#            - Variable GUID for HII type PCD\r
#            - Token space GUID for dynamicex type PCD\r
#\r
#  Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>\r
#\r
#  SPDX-License-Identifier: BSD-2-Clause-Patent\r
#\r
#\r
##\r
\r
[Defines]\r
  INF_VERSION                    = 0x00010005\r
  BASE_NAME                      = PcdPeim\r
  MODULE_UNI_FILE                = PcdPeim.uni\r
  FILE_GUID                      = 9B3ADA4F-AE56-4c24-8DEA-F03B7558AE50\r
  MODULE_TYPE                    = PEIM\r
  VERSION_STRING                 = 4.0\r
  PCD_IS_DRIVER                  = PEI_PCD_DRIVER\r
  ENTRY_POINT                    = PcdPeimInit\r
\r
#\r
# The following information is for reference only and not required by the build tools.\r
#\r
#  VALID_ARCHITECTURES           = IA32 X64 EBC (EBC is for build only)\r
#\r
\r
[Sources]\r
  Service.c\r
  Service.h\r
  Pcd.c\r
\r
[Packages]\r
  MdePkg/MdePkg.dec\r
  MdeModulePkg/MdeModulePkg.dec\r
\r
[LibraryClasses]\r
  BaseMemoryLib\r
  PcdLib\r
  PeiServicesLib\r
  HobLib\r
  BaseLib\r
  PeimEntryPoint\r
  DebugLib\r
  MemoryAllocationLib\r
\r
[Guids]\r
  ## PRODUCES            ## HOB\r
  ## SOMETIMES_CONSUMES  ## HOB\r
  gPcdDataBaseHobGuid\r
  gPcdDataBaseSignatureGuid                     ## CONSUMES  ## GUID  # PCD database signature GUID.\r
  gEfiMdeModulePkgTokenSpaceGuid                ## SOMETIMES_CONSUMES  ## GUID\r
\r
[Ppis]\r
  gEfiPeiReadOnlyVariable2PpiGuid               ## SOMETIMES_CONSUMES\r
  gPcdPpiGuid                                   ## PRODUCES\r
  gEfiPeiPcdPpiGuid                             ## PRODUCES\r
  gGetPcdInfoPpiGuid                            ## SOMETIMES_PRODUCES\r
  gEfiGetPcdInfoPpiGuid                         ## SOMETIMES_PRODUCES\r
  gEfiEndOfPeiSignalPpiGuid                     ## NOTIFY\r
\r
[FeaturePcd]\r
  gEfiMdeModulePkgTokenSpaceGuid.PcdPeiFullPcdDatabaseEnable  ## CONSUMES\r
\r
[Pcd]\r
  gEfiMdeModulePkgTokenSpaceGuid.PcdVpdBaseAddress ## SOMETIMES_CONSUMES\r
  gEfiMdeModulePkgTokenSpaceGuid.PcdVpdBaseAddress64 ## SOMETIMES_CONSUMES\r
  gEfiMdeModulePkgTokenSpaceGuid.PcdMaxPeiPcdCallBackNumberPerPcdEntry ## SOMETIMES_CONSUMES\r
  gEfiMdeModulePkgTokenSpaceGuid.PcdNvStoreDefaultValueBuffer ## SOMETIMES_CONSUMES\r
  gEfiMdeModulePkgTokenSpaceGuid.PcdSetNvStoreDefaultId       ## CONSUMES\r
\r
[Depex]\r
  TRUE\r
\r
[UserExtensions.TianoCore."ExtraFiles"]\r
  PcdPeimExtra.uni\r
Commit	Line	Data
	1	## @file\r
	2	# PCD PEIM produces PCD database to manage all dynamic PCD in PEI phase and install Pcd Ppi service.\r
	3	#\r
	4	# This version PCD PEIM depends on the external PCD database binary file, not built in PCD data base.\r
	5	# There are two PCD PPIs as follows:\r
	6	# 1) PCD_PPI\r
	7	# It is EDKII implementation which support Dynamic/DynamicEx Pcds.\r
	8	# 2) EFI_PEI_PCD_PPI\r
	9	# It is defined by PI specification 1.2, Vol 3 which only support dynamicEx\r
	10	# type Pcd.\r
	11	# For dynamicEx type PCD, it is compatible between PCD_PPI and EFI_PEI_PCD_PPI.\r
	12	# PCD PEIM driver will produce above two PPIs at same time.\r
	13	#\r
	14	# PCD database is generated as the separate binary image at build time. The binary image\r
	15	# will be intergrated into Firmware volume together with PCD driver.\r
	16	#\r
	17	# ////////////////////////////////////////////////////////////////////////////////\r
	18	# // //\r
	19	# // Introduction of PCD database //\r
	20	# // //\r
	21	# ////////////////////////////////////////////////////////////////////////////////\r
	22	#\r
	23	# 1, Introduction\r
	24	# PCD database hold all dynamic type PCD information. The structure of PEI PCD\r
	25	# database is generated by build tools according to dynamic PCD usage for\r
	26	# specified platform.\r
	27	#\r
	28	# 2, Dynamic Type PCD\r
	29	# Dynamic type PCD is used for the configuration/setting which value is determined\r
	30	# dynamic. In contrast, the value of static type PCD (FeatureFlag, FixedPcd,\r
	31	# PatchablePcd) is fixed in final generated FD image in build time.\r
	32	#\r
	33	# 2.1 The "dynamic" determination means one of below cases:\r
	34	# a) The PCD setting value is produced by someone driver and consumed by\r
	35	# other driver in execution time.\r
	36	# b) The PCD setting value is set/get by user from FrontPage.\r
	37	# c) The PCD setting value is produced by platform OEM vendor in specified area.\r
	38	#\r
	39	# 2.2 According to module distribution way, dynamic PCD could be classfied as:\r
	40	# a) Dynamic:\r
	41	# If module is released in source code and will be built with platform\r
	42	# DSC, the dynamic PCD used by this module can be accessed as:\r
	43	# PcdGetxx(PcdSampleDynamicPcd);\r
	44	# In building platform, build tools will translate PcdSampleDynamicPcd to\r
	45	# pair of {Token Space Guid: Token Number} for this PCD.\r
	46	# b) DynamicEx:\r
	47	# If module is release as binary and will not pariticpate platform building,\r
	48	# the dynamic PCD used by this module need be accessed as:\r
	49	# PcdGetxxEx(gEfiMyTokenspaceGuid, PcdSampleDynamicPcd)\r
	50	# Developer need explicity gives {Token Space Guid:Token Number} as parameter\r
	51	# in writting source code.\r
	52	#\r
	53	# 2.3 According to PCD value's storage method, dynamic PCD could be classfied as:\r
	54	# a) Default Storage:\r
	55	# - The PCD value is stored in PCD database maintained by PCD driver in boot\r
	56	# time memory.\r
	57	# - This type is used for communication between PEIM/DXE driver, DXE/DXE\r
	58	# driver. But all set/get value will be losted after boot-time memory\r
	59	# is turn off.\r
	60	# - [PcdsDynamicDefault] is used as section name for this type PCD in\r
	61	# platform DSC file. [PcdsDynamicExDefault] is used for dynamicEx type PCD.\r
	62	#\r
	63	# b) Variable Storage:\r
	64	# - The PCD value is stored in variable area.\r
	65	# - As default storage type, this type PCD could be used for PEI/DXE driver\r
	66	# communication. But beside it, this type PCD could also be used to store\r
	67	# the value associate with a HII setting via variable interface.\r
	68	# - In PEI phase, the PCD value could only be got but can not be set due\r
	69	# to variable area is readonly.\r
	70	# - [PcdsDynamicHii] is used as section name for this type PCD in platform\r
	71	# DSC file. [PcdsDynamicExHii] is for dynamicEx type PCD.\r
	72	#\r
	73	# c) OEM specificed storage area:\r
	74	# - The PCD value is stored in OEM specified area which base address is\r
	75	# specified by PCD setting - PcdVpdBaseAddress64 or PcdVpdBaseAddress.\r
	76	# - The area is read only for PEI and DXE phase.\r
	77	# - [PcdsDynamicVpd] is used as section name for this type PCD in platform\r
	78	# DSC file. [PcdsDynamicExVpd] is for dynamicex type PCD.\r
	79	#\r
	80	# 2.4 When and how to use dynamic PCD\r
	81	# Module developer do not care the used PCD is dynamic or static when writting\r
	82	# source code/INF. Dynamic PCD and dynamic type is pointed by platform integrator\r
	83	# in platform DSC file. Please ref section 2.3 to get matching between dynamic\r
	84	# PCD type and section name in DSC file.\r
	85	#\r
	86	# 3, PCD database:\r
	87	# Although dynamic PCD could be in different storage type as above description,\r
	88	# but the basic information and default value for all dynamic PCD is hold\r
	89	# by PCD database maintained by PEI/DXE driver.\r
	90	#\r
	91	# As the whole EFI BIOS boot path is divided into PEI/DXE phase, the PCD database\r
	92	# also is divided into Pei/Dxe database maintaied by PcdPeim/PcdDxe driver separatly.\r
	93	# To make PcdPeim's driver image smaller, PEI PCD database only hold all dynamic\r
	94	# PCD information used in PEI phase or use in both PEI/DXE phase. And DXE PCD\r
	95	# database contains all PCDs used in PEI/DXE phase in memory.\r
	96	#\r
	97	# Build tool will generate PCD database into the separate binary file for\r
	98	# PEI/DXE PCD driver according to dynamic PCD section in platform DSC file.\r
	99	#\r
	100	# 3.1 PcdPeim and PcdDxe\r
	101	# PEI PCD database is maintained by PcdPeim driver run from flash. PcdPeim driver\r
	102	# build guid hob in temporary memory and copy the binary data base from flash\r
	103	# to temporary memory for PEI PCD database.\r
	104	# DXE PCD database is maintained by PcdDxe driver.At entry point of PcdDxe driver,\r
	105	# a new PCD database is allocated in boot-time memory which including all\r
	106	# PEI PCD and DXE PCD entry.\r
	107	#\r
	108	# Pcd driver should run as early as possible before any other driver access\r
	109	# dynamic PCD's value. PEI/DXE "Apriori File" mechanism make it possible by\r
	110	# making PcdPeim/PcdDxe as first dispatching driver in PEI/DXE phase.\r
	111	#\r
	112	# 3.2 Token space Guid/Token number, Platform token, Local token number\r
	113	# Dynamic PCD\r
	114	# +-----------+ +---------+\r
	115	# \|TokenSpace \| \|Platform \|\r
	116	# \| Guid \| build tool \| Token \|\r
	117	# \| + +-------------->\| Number \|\r
	118	# \| Token \| +---------+`._\r
	119	# \| Number \| `.\r
	120	# +-----------+ `. +------+\r
	121	# `-\|Local \|\r
	122	# \|Token \|\r
	123	# DynamicEx PCD ,-\|Number\|\r
	124	# +-----------+ ,-' +------+\r
	125	# \|TokenSpace \| ,-'\r
	126	# \| Guid \| _,-'\r
	127	# \| + +.'\r
	128	# \| Token \|\r
	129	# \| Number \|\r
	130	# +-----------+\r
	131	#\r
	132	#\r
	133	# 3.2.1 Pair of Token space guid + Token number\r
	134	# Any type PCD is identified by pair of "TokenSpaceGuid + TokeNumber". But it\r
	135	# is not easy maintained by PCD driver, and hashed token number will make\r
	136	# searching slowly.\r
	137	#\r
	138	# 3.2.2 Platform Token Number\r
	139	# "Platform token number" concept is introduced for mapping to a pair of\r
	140	# "TokenSpaceGuid + TokenNumber". The platform token number is generated by\r
	141	# build tool in autogen.h and all of them are continual in a platform scope\r
	142	# started from 1.(0 meaning invalid internal token number)\r
	143	# With auto-generated "platform token number", PcdGet(PcdSampleDynamicPcd)\r
	144	# in source code is translated to LibPcdGet(_PCD_TOKEN_PcdSampleDynamicPcd)\r
	145	# in autogen.h.\r
	146	# Notes: The mapping between pair of "tokenspace guid + token number" and\r
	147	# "internal token number" need build tool establish, so "platform token number"\r
	148	# mechanism is not suitable for binary module which use DynamicEx type PCD.\r
	149	# To access a dynamicEx type PCD, pair of "token space guid/token number" all need\r
	150	# to be specificed for PcdSet/PcdGet accessing macro.\r
	151	#\r
	152	# Platform Token Number is started from 1, and inceased continuous. From whole\r
	153	# platform scope, there are two zones: PEI Zone and DXE Zone\r
	154	# \| Platform Token Number\r
	155	# ----------\|----------------------------------------------------------------\r
	156	# PEI Zone: \| 1 ~ PEI_LOCAL_TOKEN_NUMBER\r
	157	# DXE Zone: \| (PEI_LOCAL_TOKEN_NUMBER + 1) ~ (PEI_LOCAL_TOKEN_NUMBER + DXE_LOCAL_TOKEN_NUMBER)\r
	158	#\r
	159	# 3.2.3 Local Token Number\r
	160	# To fast searching a PCD entry in PCD database, PCD driver translate\r
	161	# platform token number to local token number via a mapping table.\r
	162	# For binary DynamicEx type PCD, there is a another mapping table to translate\r
	163	# "token space guid + token number" to local token number directly.\r
	164	# Local token number is identifier for all internal interface in PCD PEI/DXE\r
	165	# driver.\r
	166	#\r
	167	# A local token number is a 32-bit value in following meaning:\r
	168	# 32 ------------- 28 ---------- 24 -------- 0\r
	169	# \| PCD type mask \| Datum Type \| Offset \|\r
	170	# +-----------------------------------------+\r
	171	# where:\r
	172	# PCd type mask: indicate Pcd type from following macro:\r
	173	# PCD_TYPE_DATA\r
	174	# PCD_TYPE_HII\r
	175	# PCD_TYPE_VPD\r
	176	# PCD_TYPE_STRING\r
	177	# Datum Type : indicate PCD vaue type from following macro:\r
	178	# PCD_DATUM_TYPE_POINTER\r
	179	# PCD_DATUM_TYPE_UINT8\r
	180	# PCD_DATUM_TYPE_UINT16\r
	181	# PCD_DATUM_TYPE_UINT32\r
	182	# PCD_DATUM_TYPE_UINT64\r
	183	# Offset : indicate the related offset of PCD value in PCD database array.\r
	184	# Based on local token number, PCD driver could fast determine PCD type, value\r
	185	# type and get PCD entry from PCD database.\r
	186	#\r
	187	# 3.3 PCD Database binary file\r
	188	# PCD Database binary file will be created at build time as the standalone binary image.\r
	189	# To understand the binary image layout, PCD Database C structure is still generated\r
	190	# as comments by build tools in PCD driver's autogen.h/\r
	191	# autogen.c file. In generated C structure, following information is stored:\r
	192	# - ExMapTable: This table is used translate a binary dynamicex type PCD's\r
	193	# "tokenguid + token" to local token number.\r
	194	# - LocalTokenNumberTable:\r
	195	# This table stores all local token number in array, use "Internal\r
	196	# token number" as array index to get PCD entry's offset fastly.\r
	197	# - SizeTable: This table stores the size information for all PCD entry.\r
	198	# - GuidTable: This table stores guid value for DynamicEx's token space,\r
	199	# HII type PCD's variable GUID.\r
	200	# - SkuIdTable: TBD\r
	201	# - SystemSkuId: TBD\r
	202	# - PCD value structure:\r
	203	# Every PCD has a value record in PCD database. For different\r
	204	# datum type PCD has different record structure which will be\r
	205	# introduced in 3.3.1\r
	206	#\r
	207	# In a PCD database structure, there are two major area: Init and UnInit.\r
	208	# Init area is use stored above PCD internal structure such as ExMapTable,\r
	209	# LocalTokenNumberTable etc and the (default) value of PCD which has default\r
	210	# value specified in platform DSC file.\r
	211	# Unint area is used stored the value of PCD which has no default value in\r
	212	# platform DSC file, the value of NULL, 0 specified in platform DSC file can\r
	213	# be seemed as "no default value".\r
	214	#\r
	215	# 3.3.1 Simple Sample PCD Database C Structure\r
	216	# A general sample of PCD database structue is as follows:\r
	217	# typedef struct _PCD_DATABASE {\r
	218	# typedef struct _PCD_DATABASE_INIT {\r
	219	# //===== Following is PCD database internal maintain structures\r
	220	# DYNAMICEX_MAPPING ExMapTable[PEI_EXMAPPING_TABLE_SIZE];\r
	221	# UINT32 LocalTokenNumberTable[PEI_LOCAL_TOKEN_NUMBER_TABLE_SIZE];\r
	222	# GUID GuidTable[PEI_GUID_TABLE_SIZE];\r
	223	# SIZE_INFO SizeTable[PEI_SIZE_TABLE_SIZE];\r
	224	# UINT8 SkuIdTable[PEI_SKUID_TABLE_SIZE];\r
	225	# SKU_ID SystemSkuId;\r
	226	#\r
	227	# //===== Following is value structure for PCD with default value\r
	228	# ....\r
	229	# ....\r
	230	# ....\r
	231	# } Init;\r
	232	# typedef struct _PCD_DATABSE_UNINIT {\r
	233	# //==== Following is value structure for PCD without default value\r
	234	# ....\r
	235	# ....\r
	236	# } UnInit;\r
	237	# }\r
	238	#\r
	239	# 3.3.2 PCD value structure in PCD database C structure\r
	240	# The value's structure is generated by build tool in PCD database C structure.\r
	241	# The PCDs in different datum type has different value structure.\r
	242	#\r
	243	# 3.3.2.1 UINT8/UINT16/UINT32/UINT64 datum type PCD\r
	244	# The C structure for these datum type PCD is just a UINT8/UINT16/UINT32/UINT64\r
	245	# data member in PCD database, For example:\r
	246	# UINT16 PcdHardwareErrorRecordLevel_d3705011_bc19_4af7_be16_f68030378c15_VariableDefault_0;\r
	247	# Above structure is generated by build tool, the member name is "PcdCName_Guidvalue"\r
	248	# Member type is UINT16 according to PcdHardwareErrorRecordLevel declaration\r
	249	# in DEC file.\r
	250	#\r
	251	# 3.3.2.2 VOID* datum type PCD\r
	252	# The value of VOID* datum type PCD is a UINT8/UINT16 array in PCD database.\r
	253	#\r
	254	# 3.3.2.2.1 VOID* - string type\r
	255	# If the default value for VOID* datum type PCD like L"xxx", the PCD is\r
	256	# used for unicode string, and C structure of this datum type PCD is\r
	257	# UINT16 string array in PCD database, for example:\r
	258	# UINT16 StringTable[29];\r
	259	# The number of 29 in above sample is max size of a unicode string.\r
	260	#\r
	261	# If the default value for VOID* datum type PCD like "xxx", the PCD is\r
	262	# used for ascii string, and C structure of this datum type PCD is\r
	263	# UINT8 string array in PCD database, for example:\r
	264	# UINT8 StringTable[20];\r
	265	# The number of 20 in above sample is max size of a ascii string.\r
	266	#\r
	267	# 3.3.2.2.2 VOID* - byte array\r
	268	# If the default value of VOID* datum type PCD like {'0x29', '0x01', '0xf2'}\r
	269	# the PCD is used for byte array. The generated structrue is same as\r
	270	# above ascii string table,\r
	271	# UINT8 StringTable[13];\r
	272	# The number of 13 in above sample is max size of byte array.\r
	273	#\r
	274	# 3.3.3 Some utility structures in PCD Database\r
	275	# 3.3.3.1 GuidTable\r
	276	# GuidTable array is used to store all related GUID value in PCD database:\r
	277	# - Variable GUID for HII type PCD\r
	278	# - Token space GUID for dynamicex type PCD\r
	279	#\r
	280	# Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>\r
	281	#\r
	282	# SPDX-License-Identifier: BSD-2-Clause-Patent\r
	283	#\r
	284	#\r
	285	##\r
	286	\r
	287	[Defines]\r
	288	INF_VERSION = 0x00010005\r
	289	BASE_NAME = PcdPeim\r
	290	MODULE_UNI_FILE = PcdPeim.uni\r
	291	FILE_GUID = 9B3ADA4F-AE56-4c24-8DEA-F03B7558AE50\r
	292	MODULE_TYPE = PEIM\r
	293	VERSION_STRING = 4.0\r
	294	PCD_IS_DRIVER = PEI_PCD_DRIVER\r
	295	ENTRY_POINT = PcdPeimInit\r
	296	\r
	297	#\r
	298	# The following information is for reference only and not required by the build tools.\r
	299	#\r
	300	# VALID_ARCHITECTURES = IA32 X64 EBC (EBC is for build only)\r
	301	#\r
	302	\r
	303	[Sources]\r
	304	Service.c\r
	305	Service.h\r
	306	Pcd.c\r
	307	\r
	308	[Packages]\r
	309	MdePkg/MdePkg.dec\r
	310	MdeModulePkg/MdeModulePkg.dec\r
	311	\r
	312	[LibraryClasses]\r
	313	BaseMemoryLib\r
	314	PcdLib\r
	315	PeiServicesLib\r
	316	HobLib\r
	317	BaseLib\r
	318	PeimEntryPoint\r
	319	DebugLib\r
	320	MemoryAllocationLib\r
	321	\r
	322	[Guids]\r
	323	## PRODUCES ## HOB\r
	324	## SOMETIMES_CONSUMES ## HOB\r
	325	gPcdDataBaseHobGuid\r
	326	gPcdDataBaseSignatureGuid ## CONSUMES ## GUID # PCD database signature GUID.\r
	327	gEfiMdeModulePkgTokenSpaceGuid ## SOMETIMES_CONSUMES ## GUID\r
	328	\r
	329	[Ppis]\r
	330	gEfiPeiReadOnlyVariable2PpiGuid ## SOMETIMES_CONSUMES\r
	331	gPcdPpiGuid ## PRODUCES\r
	332	gEfiPeiPcdPpiGuid ## PRODUCES\r
	333	gGetPcdInfoPpiGuid ## SOMETIMES_PRODUCES\r
	334	gEfiGetPcdInfoPpiGuid ## SOMETIMES_PRODUCES\r
	335	gEfiEndOfPeiSignalPpiGuid ## NOTIFY\r
	336	\r
	337	[FeaturePcd]\r
	338	gEfiMdeModulePkgTokenSpaceGuid.PcdPeiFullPcdDatabaseEnable ## CONSUMES\r
	339	\r
	340	[Pcd]\r
	341	gEfiMdeModulePkgTokenSpaceGuid.PcdVpdBaseAddress ## SOMETIMES_CONSUMES\r
	342	gEfiMdeModulePkgTokenSpaceGuid.PcdVpdBaseAddress64 ## SOMETIMES_CONSUMES\r
	343	gEfiMdeModulePkgTokenSpaceGuid.PcdMaxPeiPcdCallBackNumberPerPcdEntry ## SOMETIMES_CONSUMES\r
	344	gEfiMdeModulePkgTokenSpaceGuid.PcdNvStoreDefaultValueBuffer ## SOMETIMES_CONSUMES\r
	345	gEfiMdeModulePkgTokenSpaceGuid.PcdSetNvStoreDefaultId ## CONSUMES\r
	346	\r
	347	[Depex]\r
	348	TRUE\r
	349	\r
	350	[UserExtensions.TianoCore."ExtraFiles"]\r
	351	PcdPeimExtra.uni\r