zynqmp_pm_debugfs_api_write(9)

💅 zynqmp_pm_debugfs_api_write 💅

okay bestie, real talk — this is a page out of the Kernel API Manual, and it's about zynqmp_pm_debugfs_api_write(9). yes the name is a mouthful, no we're not renaming it, periodt. 🎀

---

✨ NAME ✨

zynqmp_pm_debugfs_api_write — the debugfs write function. that's it, that's the whole vibe 🦋

---

🌸 SYNOPSIS 🌸

ssize_t zynqmp_pm_debugfs_api_write (struct file *file , const char
__user *ptr , size_t len , loff_t *off );

like literally look at her. icon behavior. 👑

---

🧚 ARGUMENTS 🧚

• file — the user file, just hanging out, being a file 🫶
• ptr — the PM-API string that the user typed in (yes, from userspace, protected, careful bb) ✨
• len — how long the userspace buffer is, in case you were wondering 📏
• off — where you are inside the file, the offset, the position, the moment 💫

---

💖 DESCRIPTION 💖

so what does she actually do? she's the one that triggers pm api functions, and the way you do it is genuinely so simple it's giving main character energy:

echo <pm_api_id>   > /sys/kernel/debug/zynqmp_pm/power

or, if you're feeling spicy and prefer names over numbers:

echo <pm_api_name> > /sys/kernel/debug/zynqmp_pm/power

yep, both work — id or name, your call, no cap. 💅

---

🔥 RETURN 🔥

• if the PM-API request goes through — you get the number of bytes copied ✨ slay
• if it doesn't — you get the corresponding error code 😭 not slay, but at least she told you

---

🌈 SEE ALSO 🌈

go read the kernel file ./drivers/firmware/xilinx/zynqmp-debug.c (iykyk 💜) and also these besties:

• zynqmp_pm_ioctl(9)
• zynqmp_pm_argument_value(9)
• get_pm_api_id(9)
• zynqmp_pm_debugfs_api_read(9)
• zynqmp_pm_api_debugfs_init(9)
• zynqmp_pm_api_debugfs_exit(9)

---

okay that's the whole page, mwah 💋 — this masterpiece lives in ./drivers/firmware/xilinx, dated October 2026, and it'll always be zynqmp_pm_debugfs_api_write(9) to us. go forth and echo responsibly, bestie 🍓💖