diff options
| author | Pierre Gondois <pierre.gondois@arm.com> | 2024-01-29 13:09:35 +0100 |
|---|---|---|
| committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2024-01-29 16:47:03 +0000 |
| commit | dc3339470166884197e9be5a6b3e7afe13104f1f (patch) | |
| tree | 7a34d5a77229327937ac676e1d25a2fc053b9e59 /PcAtChipsetPkg | |
| parent | dec9d3573829ac020e34d19a4f39d3154f066379 (diff) | |
| download | edk2-dc3339470166884197e9be5a6b3e7afe13104f1f.tar.gz edk2-dc3339470166884197e9be5a6b3e7afe13104f1f.tar.bz2 edk2-dc3339470166884197e9be5a6b3e7afe13104f1f.zip | |
DynamicTablesPkg: Exempt some _CPC field from checks
When generating _CPC objects, some fields are mandatory by spec [1].
Some fields cannot be supported by a the Juno platform, which is used
to test the _CPC generation. Therefore, rely on the
PcdDevelopmentPlatformRelaxations Pcd to either:
- warn about the missing fields and and let the OS handle the
missing information
- consider the missing fields as an error
_CPC fields that are exempted from checks when the Pcd is set:
- PerformanceLimitedRegister
- ReferencePerformanceCounterRegister
- DeliveredPerformanceCounterRegister
[1] Cf. non-optional fields in:
ACPI 6.5, s8.4.6.1 '_CPC (Continuous Performance Control)'
Signed-off-by: Pierre Gondois <pierre.gondois@arm.com>
Reviewed-by: Sami Mujawar <sami.mujawar@arm.com>
Diffstat (limited to 'PcAtChipsetPkg')
0 files changed, 0 insertions, 0 deletions