Tianocore/edk2.git/MdeModulePkg/MdeModulePkg.dec, branch dependabot/github_actions/actions/github-script-9

Revert "ArmPlatformPkg,EmbeddedPkg,MdeModulePkg: Move RealTimeClockLib ..."

2026-05-06T03:41:31+00:00

This reverts commit 57230fff6b39a665485be1bd43ec608d412ba6fb. RealTimeClockLib is not a generic library class that is intended to be used widely to get access to the RTC when the associated runtime services are not available in the calling context. The purpose of RealTimeClockLib is to abstract the underlying hardware access from the generic RealTimeClockRuntimeDxe driver, which backs the runtime services. This means it does not belong in a different package; it belongs in the same package as the driver. Continuous-integration-options: PatchCheck.ignore-multi-package Signed-off-by: Ard Biesheuvel

MdeModulePkg: Add CxlIo.h protocol

2026-05-01T06:48:04+00:00

Create a CXL protocol for interacting with CXL endpoint devices. CXL devices are necessarily also PCI devices, so the PCI IO protocol is also provided as part of the CXL protocol. The protocol provides access to the following operations for CXL devices: - Read from a DVSEC register block - Write to a DVSEC register block - Perform DOE transaction This set of operation is sufficient to implement BIOS-level CXL functionality. Signed-off-by: Nick Graves Signed-off-by: Oleksandr Tymoshenko

MdeModulePkg: Don't Allow Guard Pages to Cross Bin Boundaries

2026-04-23T02:42:12+00:00

Currently, the DXE page allocator does not ensure that guard page allocations stay within the bin that it is attempting to allocate within. As a result, S4 resume is jeopardized by bins expanding due to guard pages, either into other bins or out of bins. This is caught by a new assert in CoreGetMemoryMap() to ensure the bins are correct. This fixes this by changing the internal heap guard API to return the adjusted size and start address of a proposed allocation. The page allocator then can ensure that the adjusted allocation still fits within the bin it is attempting to allocate within; if not, it will search for another descriptor. Signed-off-by: Oliver Smith-Denny

MdeModulePkg/NetworkCommon: Add PCD for USB network periodic timer

2026-04-21T13:29:12+00:00

Replace the hardcoded NETWORK_COMMON_POLLING_INTERVAL (0x10 = 16ms) with a new PCD PcdUsbNetworkPeriodicalTimer, allowing platforms to configure the asynchronous transfer interval for USB network devices. The default value of 16ms preserves existing behaviour. EFI_USB_IO_PROTOCOL.UsbAsyncInterruptTransfer(), the PollingInterval parameter must be between 1 and 255 milliseconds; a value of 0 returns EFI_INVALID_PARAMETER. The PCD is declared with a @ValidRange of 1-255 and an ASSERT guards against a zero value at runtime. Co-authored-by: Abner Chang Signed-off-by: Abdul Lateef Attar

MdeModulePkg/PciBusDxe: Add optional CRS retry for enumeration

2026-03-17T02:03:32+00:00

The current PciDevicePresent() implementation skips PCIe devices that return Configuration Request Retry Status (CRS) during enumeration. This causes devices that are slow to initialize (e.g., after power-on or reset) to be missed entirely. Per PCIe Base Specification Rev 3.1 Section 2.3.1, when CRS Software Visibility is enabled and a device returns CRS, the Root Complex reports Vendor ID as 0x0001. The specification recommends software retry the configuration read until the device becomes ready. This patch adds optional CRS retry support controlled by PCDs: - PcdPciCrsRetryIntervalUs: Retry interval in microseconds (default 10000) - PcdPciCrsTimeoutSeconds: Total timeout in seconds (default 0) By default (PcdPciCrsTimeoutSeconds=0), CRS retry is disabled and devices returning CRS are skipped during enumeration. Platforms requiring CRS retry support should set PcdPciCrsTimeoutSeconds to a non-zero value. Additional improvements: - Add PCI_VENDOR_ID_NONE and PCI_VENDOR_ID_CRS macros for readability - Handle invalid PCD configurations (e.g., zero retry interval) - Add DEBUG output for CRS detection, successful retry, and timeout Signed-off-by: Ashish Singhal

MdeModulePkg: Mark PcdMrIovSupport obsolete - deprecated in PCIe 6.0

2026-02-25T05:03:02+00:00

MR-IOV was actually not used in MdeModulePkg and it has been deprecated in PCIe 6.0 specification. Remove code references, but keep PcdMrIovSupport with just a comment that it is deprecated. Signed-off-by: Jacek Kolakowski

MdeModulePkg: Add platform limit for size in Resizable BAR

2026-02-25T03:40:14+00:00

Resizable BAR driver selects max available BAR size to configure for use. It may happen that some PCIe device declare support for size that exceeds processor address width. Platform needs a way to define the max size it can accept. This change introduce PCD called PcdPcieResizableBarMaxSize. It is dynamic PCD where platform can provide its limit for BAR size. Such PCD can be also controlled with a configuration knob. Signed-off-by: Jacek Kolakowski

MdeModulePkg: BdsDxe: Introduce infinite boot retries

2026-02-02T02:24:18+00:00

This PR introduces a new feature to enable infinite boot retries based on a newly created PCD. When true, the system will continuously loop over all boot options. PCD default is FALSE to match existing functionality. This change is tested on QEMU based virtual platforms and physical platforms. This change is useful for certain server cases. Infinite retries allows a server to continuously attempt boot in case of network failure and recovery, and for such attempts to be accurately recorded in the TCG logs. Co-authored-by: Kun Qin Co-authored-by: Aaron Pop Co-authored-by: Michael Kubacki Signed-off-by: Sherry Fan

MdeModulePkg: Define PCD for SATA ready for operation timeout.

2025-11-22T17:01:23+00:00

Some large capacity SATA HDD requires more time from power on to ready state. Making timeout value configurable by defining PCD PcdSataDeviceReadyTimeout will allow platform.dsc to serve these devices. Defining gEfiMdeModulePkgTokenSpaceGuid.PcdSataDeviceReadyTimeout with default value 16 Seconds in MdeModulePkg.dec. Signed-off-by: gapandya

MdeModulePkg/DxeCapsuleLibFmp:Added PCD for EmbeddedDriver Support

2025-10-14T17:45:19+00:00

Currently, there is no mechanism for platforms to enable or disable support for EmbeddedDrivers in capsule updates. This patch introduces a new PCD, PcdEmbeddedDriverSupport, allowing platforms to explicitly control whether capsules containing EmbeddedDrivers are supported. This ensures capsules with embedded drivers are rejected on platforms that do not support them. This is a breaking change.By default, PcdEmbeddedDriverSupport is set to FALSE which disables embedded driver support in capsule updates across all platforms unless explicitly enabled. Platforms must opt-in by setting the PcdEmbeddedDriverSupport to TRUE in order to enable support for capsules containing embedded drivers. Signed-off-by: Pavithra Gurulingappa