zynqmp_pm_aes_engine(9)

💅 zynqmp_pm_aes_engine(9)

okay so bestie, welcome to the Kernel API Manual — yes this is a real manpage from the kernel and yes we're gonna get through it together, no cap. ✨

---

🌸 NAME 🌸

zynqmp_pm_aes_engine — this is the glow-up function that gets you access to the AES hardware so you can encrypt/decrypt your data using the AES-GCM core. it's giving hardware-accelerated crypto realness. 🔥

---

🎀 SYNOPSIS 🎀

int zynqmp_pm_aes_engine (const u64 address , u32 *out );

like, that's the whole signature. two args, one int coming back at you. periodt. 💅

---

🦋 ARGUMENTS 🦋

• address — the address of the AesParams structure. literally just where your params live in memory, that's the vibe. 📍
• out — the returned output value. this is where the output goes, bestie. 🫶

---

⭐ RETURN ⭐

returns a status — either success or an error code. so like, do a vibe check on that return value, mmkay? 😭

---

👑 SEE ALSO 👑

• Kernel file ./drivers/firmware/xilinx/zynqmp-crypto.c — go read the source, iykyk 📂
• zynqmp_pm_sha_hash(9)
• xlnx_get_crypto_dev_data(9)
• versal_pm_aes_key_write(9)
• versal_pm_aes_key_zero(9)
• versal_pm_aes_op_init(9)
• versal_pm_aes_update_aad(9)
• versal_pm_aes_enc_update(9)
• versal_pm_aes_enc_final(9)
• versal_pm_aes_dec_update(9)
• versal_pm_aes_dec_final(9)
• versal_pm_aes_init(9)

like a whole friend group of crypto functions. iconic. 🌈

---

ngl, if you're messing with the AES engine you should probably at least skim the AES-GCM core docs too — but that's just me being a good bestie. 🧚

---

and that's the page! brought to you from ./drivers/firmware/xilinx, dated October 2026 — mwah, take care of yourself and your crypto, bestie 💖🎀🦋