]>
Commit | Line | Data |
---|---|---|
6bfbb5f0 | 1 | ## @file\r |
2621e6ca | 2 | # PCD DXE driver manage database contains all dynamic PCD entries initialized in \r |
3 | # PEI phase, DXE phase and produce the implementation of PCD protocol.\r | |
6c74c538 | 4 | #\r |
5 | # There are two PCD Protocols as follows:\r | |
6 | # 1) PCD_PROTOCOL \r | |
7 | # It is EDKII implementation which support Dynamic/DynamicEx type Pcds.\r | |
8 | # 2) EFI_PCD_PROTOCOL_PPI\r | |
9 | # It is defined by PI specification 1.2, Vol 3 which only support dynamicEx \r | |
10 | # type Pcd.\r | |
11 | #\r | |
12 | # For dynamicEx type PCD, it is compatible between PCD_PPI and EFI_PEI_PCD_PPI. \r | |
13 | # PCD DXE driver will produce above two protocols at same time.\r | |
14 | #\r | |
2621e6ca | 15 | # PCD database structure is generated at autogen.h/autogen.c in build time.\r |
80408db0 | 16 | #\r |
b6b3dc44 | 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 alsp 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 a FixedAtBuild PCD setting - 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 some C structure and variable 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 auto-generated C structure \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_SKU_ENABLED\r | |
177 | # PCD_TYPE_STRING\r | |
178 | # Datum Type : indicate PCD vaue type from following macro:\r | |
179 | # PCD_DATUM_TYPE_POINTER\r | |
180 | # PCD_DATUM_TYPE_UINT8\r | |
181 | # PCD_DATUM_TYPE_UINT16\r | |
182 | # PCD_DATUM_TYPE_UINT32\r | |
183 | # PCD_DATUM_TYPE_UINT64\r | |
184 | # Offset : indicate the related offset of PCD value in PCD database array.\r | |
185 | # Based on local token number, PCD driver could fast determine PCD type, value\r | |
186 | # type and get PCD entry from PCD database.\r | |
187 | # \r | |
188 | # 3.3 PCD Database C structure.\r | |
189 | # PCD Database C structure is generated by build tools in PCD driver's autogen.h/\r | |
190 | # autogen.c file. In generated C structure, following information is stored:\r | |
191 | # - ExMapTable: This table is used translate a binary dynamicex type PCD's \r | |
192 | # "tokenguid + token" to local token number.\r | |
193 | # - LocalTokenNumberTable:\r | |
194 | # This table stores all local token number in array, use "Internal\r | |
195 | # token number" as array index to get PCD entry's offset fastly.\r | |
196 | # - SizeTable: This table stores the size information for all PCD entry.\r | |
197 | # - GuidTable: This table stores guid value for DynamicEx's token space,\r | |
198 | # HII type PCD's variable.\r | |
199 | # - SkuIdTable: TBD\r | |
200 | # - SystemSkuId: TBD\r | |
201 | # - PCD value structure: \r | |
202 | # Every PCD has a value record in PCD database. For different\r | |
203 | # datum type PCD has different record structure which will be \r | |
204 | # introduced in 3.3.1\r | |
205 | # \r | |
206 | # In a PCD database structure, there are two major area: Init and UnInit. \r | |
207 | # Init area is use stored above PCD internal structure such as ExMapTable, \r | |
208 | # LocalTokenNumberTable etc and the (default) value of PCD which has default \r | |
209 | # value specified in platform DSC file.\r | |
210 | # Unint area is used stored the value of PCD which has no default value in\r | |
211 | # platform DSC file, the value of NULL, 0 specified in platform DSC file can\r | |
212 | # be seemed as "no default value".\r | |
213 | # \r | |
214 | # 3.3.1 Simple Sample PCD Database C Structure\r | |
215 | # A general sample of PCD database structue is as follows:\r | |
216 | # typedef struct _PCD_DATABASE {\r | |
217 | # typedef struct _PCD_DATABASE_INIT {\r | |
218 | # //===== Following is PCD database internal maintain structures\r | |
219 | # DYNAMICEX_MAPPING ExMapTable[PEI_EXMAPPING_TABLE_SIZE];\r | |
220 | # UINT32 LocalTokenNumberTable[PEI_LOCAL_TOKEN_NUMBER_TABLE_SIZE];\r | |
221 | # GUID GuidTable[PEI_GUID_TABLE_SIZE];\r | |
222 | # SIZE_INFO SizeTable[PEI_SIZE_TABLE_SIZE];\r | |
223 | # UINT8 SkuIdTable[PEI_SKUID_TABLE_SIZE];\r | |
224 | # SKU_ID SystemSkuId;\r | |
225 | # \r | |
226 | # //===== Following is value structure for PCD with default value\r | |
227 | # ....\r | |
228 | # ....\r | |
229 | # ....\r | |
230 | # } Init;\r | |
231 | # typedef struct _PCD_DATABSE_UNINIT {\r | |
232 | # //==== Following is value structure for PCD without default value\r | |
233 | # ....\r | |
234 | # ....\r | |
235 | # } UnInit;\r | |
236 | # }\r | |
237 | # \r | |
238 | # 3.3.2 PCD value structure in PCD database C structure\r | |
239 | # The value's structure is generated by build tool in PCD database C structure.\r | |
240 | # The PCDs in different datum type has different value structure.\r | |
241 | # \r | |
242 | # 3.3.2.1 UINT8/UINT16/UINT32/UINT64 datum type PCD\r | |
243 | # The C structure for these datum type PCD is just a UINT8/UINT16/UINT32/UINT64\r | |
244 | # data member in PCD database, For example:\r | |
245 | # UINT16 PcdHardwareErrorRecordLevel_d3705011_bc19_4af7_be16_f68030378c15_VariableDefault_0;\r | |
246 | # Above structure is generated by build tool, the member name is "PcdCName_Guidvalue"\r | |
247 | # Member type is UINT16 according to PcdHardwareErrorRecordLevel declaration\r | |
248 | # in DEC file.\r | |
249 | # \r | |
250 | # 3.3.2.2 VOID* datum type PCD\r | |
251 | # The value of VOID* datum type PCD is a UINT8/UINT16 array in PCD database.\r | |
252 | # \r | |
253 | # 3.3.2.2.1 VOID* - string type\r | |
254 | # If the default value for VOID* datum type PCD like L"xxx", the PCD is \r | |
255 | # used for unicode string, and C structure of this datum type PCD is \r | |
256 | # UINT16 string array in PCD database, for example:\r | |
257 | # UINT16 StringTable[29];\r | |
258 | # The number of 29 in above sample is max size of a unicode string.\r | |
259 | # \r | |
260 | # If the default value for VOID* datum type PCD like "xxx", the PCD is\r | |
261 | # used for ascii string, and C structure of this datum type PCD is \r | |
262 | # UINT8 string array in PCD database, for example:\r | |
263 | # UINT8 StringTable[20];\r | |
264 | # The number of 20 in above sample is max size of a ascii string.\r | |
265 | # \r | |
266 | # 3.3.2.2.2 VOID* - byte array\r | |
267 | # If the default value of VOID* datum type PCD like {'0x29', '0x01', '0xf2'}\r | |
268 | # the PCD is used for byte array. The generated structrue is same as \r | |
269 | # above ascii string table,\r | |
270 | # UINT8 StringTable[13];\r | |
271 | # The number of 13 in above sample is max size of byte array.\r | |
272 | # \r | |
273 | # 3.3.3 Some utility structures in PCD Database\r | |
274 | # 3.3.3.1 GuidTable\r | |
275 | # GuidTable array is used to store all related GUID value in PCD database:\r | |
276 | # - Variable GUID for HII type PCD\r | |
277 | # - Token space GUID for dynamicex type PCD \r | |
278 | #\r | |
e5eed7d3 | 279 | # Copyright (c) 2006 - 2010, Intel Corporation. All rights reserved.<BR>\r |
80408db0 | 280 | #\r |
e5eed7d3 | 281 | # This program and the accompanying materials\r |
80408db0 | 282 | # are licensed and made available under the terms and conditions of the BSD License\r |
283 | # which accompanies this distribution. The full text of the license may be found at\r | |
284 | # http://opensource.org/licenses/bsd-license.php\r | |
285 | # THE PROGRAM IS DISTRIBUTED UNDER THE BSD LICENSE ON AN "AS IS" BASIS,\r | |
286 | # WITHOUT WARRANTIES OR REPRESENTATIONS OF ANY KIND, EITHER EXPRESS OR IMPLIED.\r | |
287 | #\r | |
288 | #\r | |
6bfbb5f0 | 289 | ##\r |
80408db0 | 290 | \r |
80408db0 | 291 | [Defines]\r |
292 | INF_VERSION = 0x00010005\r | |
293 | BASE_NAME = PcdDxe\r | |
294 | FILE_GUID = 80CF7257-87AB-47f9-A3FE-D50B76D89541\r | |
295 | MODULE_TYPE = DXE_DRIVER\r | |
296 | VERSION_STRING = 1.0\r | |
be82f9ff | 297 | PCD_IS_DRIVER = DXE_PCD_DRIVER\r |
80408db0 | 298 | ENTRY_POINT = PcdDxeInit\r |
299 | \r | |
300 | #\r | |
301 | # The following information is for reference only and not required by the build tools.\r | |
302 | #\r | |
303 | # VALID_ARCHITECTURES = IA32 X64 IPF EBC\r | |
304 | #\r | |
305 | \r | |
188e4e84 | 306 | [Sources]\r |
80408db0 | 307 | Pcd.c\r |
308 | Service.c\r | |
309 | Service.h\r | |
80408db0 | 310 | \r |
311 | [Packages]\r | |
312 | MdePkg/MdePkg.dec\r | |
e75fe0eb | 313 | MdeModulePkg/MdeModulePkg.dec\r |
80408db0 | 314 | \r |
315 | [LibraryClasses]\r | |
316 | UefiRuntimeServicesTableLib\r | |
317 | BaseMemoryLib\r | |
318 | UefiBootServicesTableLib\r | |
319 | MemoryAllocationLib\r | |
320 | HobLib\r | |
80408db0 | 321 | UefiDriverEntryPoint\r |
322 | UefiLib\r | |
323 | DebugLib\r | |
324 | BaseLib\r | |
cba9012a | 325 | PcdLib\r |
80408db0 | 326 | \r |
80408db0 | 327 | [Guids]\r |
b9982883 | 328 | gPcdDataBaseHobGuid ## CONSUMES ## Hob: GUID_EXTENSION\r |
80408db0 | 329 | \r |
80408db0 | 330 | [Protocols]\r |
b9982883 | 331 | gPcdProtocolGuid ## PRODUCES\r |
c896d682 | 332 | gEfiPcdProtocolGuid ## PRODUCES\r |
333 | \r | |
188e4e84 | 334 | [Pcd]\r |
b3af5df6 | 335 | gEfiMdeModulePkgTokenSpaceGuid.PcdVpdBaseAddress\r |
80408db0 | 336 | \r |
80408db0 | 337 | [Depex]\r |
338 | TRUE\r | |
339 | \r |