zynqmp_gpd_i..._wakeup_path(9)

💖 zynqmp_gpd_is_active_wakeup_path(9) 💖

okay bestie, so this one lives in the Kernel API Manual and it's literally called zynqmp_gpd_is_active_wakeup_path — yes, the header up top squishes it down to zynqmp_gpd_i..._wakeup_path(9) because even manpage typesetting has a size limit, but we know her full name 💅

---

✨ NAME ✨

zynqmp_gpd_is_active_wakeup_path — the little detective that checks if a device is in the wakeup source path 🕵️‍♀️

---

🌸 SYNOPSIS 🌸

int zynqmp_gpd_is_active_wakeup_path (struct device *dev , void *not_used );

like, that's the whole signature, no cap 🫶

---

🎀 ARGUMENTS 🎀

• dev — the device we're checking for the wakeup source path 🦋
• not_used — a data member that is not required — she's just there, existing, iconic, doing nothing 💀

---

👑 DESCRIPTION 👑

so what she does is: she checks the device's child hierarchy and checks if any device in there is set as wakeup source ✨ that's it, that's the vibe check 🌈

---

⭐ RETURN ⭐

• 1 if the device is in the wakeup source path
• 0 otherwise

fr fr, that's the whole scale — binary, no in-between 🙈

---

🧚 SEE ALSO 🧚

• the kernel file ./drivers/pmdomain/xilinx/zynqmp-pm-domains.c 👀
• struct zynqmp_pm_domain(9)
• zynqmp_gpd_power_on(9)
• zynqmp_gpd_power_off(9)
• zynqmp_gpd_attach_dev(9)
• zynqmp_gpd_detach_dev(9)

---

go read the whole squad if you wanna actually understand the pm-domain situation, bestie — this one's just the wakeup-path girlie of the group 💅

---

and that's a wrap, babe 🎀 this page came from ./drivers/pmdomain/xilinx, dated October 2026, and the manual header still says zynqmp_gpd_i..._wakeup_path(9) — she's giving truncated but still stunning ✨ love that for her, mwah 💖