Platform Management Layers - 2025.1 English - UG1304

Versal Adaptive SoC System Software Developers Guide (Versal AI Edge Series Gen 2 and Versal Prime Series Gen 2) (UG1304)
Document ID
UG1304
Release Date
2025-06-23
Version
2025.1 English

The following API layers are included in the platform management implementation for the Versal devices:

XilPM (client)
Library layer used by standalone applications in the different processing units, such as the APU, RPU, and PL-MicroBlaze.
Note: For PL-MicroBlaze only the following APIs are supported:
  • GetApiVersion
  • DevIoctl
  • DevIoctl2
XilPM (server)
Library layer part of the PLM that handles the requests that are passed from the XilPM client layer through IPIs.
Note: This is not applicable for Versal AI Edge Series Gen 2 and Versal Prime Series Gen 2 devices. Refer Xilpm_ng for these devices.
Xilpm_ng
Library layer part of the PLM that handles the requests that are passed from the XilPM client layer through IPIs. XilPM_ng can be configured to handle only boot related requests or to handle only EEMI requests or to handle subsystem related requests.
TF-A
The TF-A contains its own implementation of the client-side PM framework. It is currently used by the Linux OS.
PLM
The PLM receives IPI packets and passes platform management requests to the XilPM server.
PSM Firmware
Invoked by the XilPM server to control power islands and power domains of PS.
Note: PSM is not applicable for Versal AI Edge Series Gen 2 and Versal Prime Series Gen 2devices.

For more details on PMC, PSM, and power domain hardware topics, see the Versal Adaptive SoC Technical Reference Manual (AM011) for Versal or Versal AI Edge Series Gen 2 and Prime Series Gen 2 Technical Reference Manual (AM026) for Versal AI Edge Series Gen 2 and Versal Prime Series Gen 2 devices.

The following figure shows the interaction between the APU, the RPU, and the platform management APIs.

Figure 1. API Layers Used Only With Bare-Metal Applications

If the APU runs a complete software stack with an operating system, it does not use the XilPM library. Instead, the TF-A running at EL3 implements the client-side XilPM API and provides a secure monitor call (SMC)-based interface to the software running at EL2, SEL1, or EL1 depending on the system architecture of Versal devices.

For more details on the Armv8 architecture and its different execution modes, see Execution Modes.

The following figure illustrates the platform management layers that are involved when running a full software stack on the APU.

Figure 2. Platform Management Layers Involved When Running a Full Software Stack on the APU