zynqmp_pm_invoke_fn(9)

📦 version 7.3.1, in nixpkgs unstable

💅 zynqmp_pm_invoke_fn — kernel API manual

Okay bestie, so this page is literally all about zynqmp_pm_invoke_fn — it's the Kernel API Manual entry for invoking the system-level platform management layer caller function, and the way it works depends on your configuration. No cap, it's giving "gateway to the firmware" energy. 🫶

✨ NAME ✨

zynqmp_pm_invoke_fn — invoke the system-level platform management layer caller function depending on the configuration. Periodt. 💅

🛠 SYNOPSIS 🛠

int zynqmp_pm_invoke_fn (u32 pm_api_id , u32 *ret_payload , u32 num_args
, ... );

🎀 ARGUMENTS 🎀

  • pm_api_id — the requested PM-API call. Like, which vibe are we asking the firmware for? 👑
  • ret_payload — returned value array. This is where the answer lands, bestie. 📦
  • num_args — number of arguments to the requested PM-API call. Gotta count them fr fr.
  • ... — variable arguments. Surprise extras, iykyk. 🎁

🌸 DESCRIPTION 🌸

So basically this function invokes the platform management function for SMC or HVC call, depending on configuration. It follows the SMC Calling Convention (SMCCC) for SMC64, and the formula is literally:

Pm Function Identifier, PM_SIP_SVC + PM_API_ID =
((SMC_TYPE_FAST << FUNCID_TYPE_SHIFT)
((SMC_64) << FUNCID_CC_SHIFT)
((SIP_START) << FUNCID_OEN_SHIFT)
((PM_API_ID) & FUNCID_NUM_MASK))

Let me break it down, bestie:

  • PM_SIP_SVC — Registered ZynqMP SIP Service Call.
  • PM_API_ID — Platform Management API ID.

That's the whole lore. It's not doing extra, it's just packing the right bits so the firmware knows what's up. 🧚

🔥 RETURN 🔥

Returns status, either success or error+reason. So like, either "slay, we're good" or "here's why not." 💀

🦋 SEE ALSO 🦋

Kernel file ./drivers/firmware/xilinx/zynqmp.c and all these besties:

This page is from ./drivers/firmware/xilinx and was last updated in October 2026. Stay slay, bestie — now go invoke some PM-APIs responsibly 💖✨🎀

📦 where this page comes from