zynqmp_pm_get_node_status(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… zynqmp_pm_get_node_status(9) β€” Kernel API Manual core πŸ’–

okay bestie, gather round. this is the Kernel API Manual page for zynqmp_pm_get_node_status, and it's literally the PM call to request a node's current power state. no cap, it's giving β€œpower-status check, but make it kernel.” ✨


🌸 NAME 🌸

zynqmp_pm_get_node_status β€” PM call to request a node's current power state.

✨ SYNOPSIS ✨

int zynqmp_pm_get_node_status (const u32 node , u32 *const status , u32
*const requirements , u32 *const usage );

Lowkey that line break is exactly how the manpage serves it, and we're keeping it. 🫢

πŸŽ€ ARGUMENTS πŸŽ€

  • node β€” ID of the component or sub-system in question. It's the β€œwho are we checking?” param. πŸ’…
  • status β€” Current operating state of the requested node. The main-character output, periodt. πŸ‘‘
  • requirements β€” Current requirements asserted on the node, used for slave nodes only. Bestie, that β€œslave nodes only” is important. 🎯
  • usage β€” Usage information, used for slave nodes only. This one comes with its own little enum moment:
    • PM_USAGE_NO_MASTER β€” No master is currently using the node.
    • PM_USAGE_CURRENT_MASTER β€” Only requesting master is currently using the node.
    • PM_USAGE_OTHER_MASTER β€” Only other masters are currently using the node.
    • PM_USAGE_BOTH_MASTERS β€” Both the current and at least one other master is currently using the node.

πŸ’– RETURN πŸ’–

Returns status, either success or error+reason. That's the whole vibe: success or error+reason. No in-between. πŸ’€

πŸ¦‹ SEE ALSO πŸ¦‹

This is the part where the manpage says β€œgo read the whole friend group” β€” every single reference from the original is here, no gatekeeping:


mwah πŸ’‹ this little page lives in the source/version corner ./drivers/firmware/xilinx, and the footer date is October 2026. zynqmp_pm_get_node_status(9) signing off β€” slay responsibly. πŸ’…βœ¨

πŸ“¦ where this page comes from