zynqmp_pm_g..._node_status(9)

💅 zynqmp_pm_g..._node_status(9) 💅

okay bestie, welcome to the Kernel API Manual corner for zynqmp_pm_g..._node_status(9) — section 9, obviously. This is the page for the PM call that asks for an RPU node’s current power state, and no cap, it’s lowkey iconic. 💖

✨ NAME ✨

zynqmp_pm_get_rpu_node_status — PM call to request a RPU node's current power state. periodt.

🌸 SYNOPSIS 🌸

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

🎀 ARGUMENTS 🎀

• node — ID of the RPU component or sub-system in question. yes, that exact one.
• status — Current operating state of the requested RPU node. (the vibe check result 💅)
• requirements — Current requirements asserted on the RPU node.
• usage — Usage information, used for RPU slave nodes only. The possible little values are:
  • 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 💖

It returns status, either success or error+reason. So basically: slay or spill the error, no in-between. 😭

👑 SEE ALSO 👑

This is the friend group. All of them. Do not skip a single one or the manpage gremlins will come for us 💀:

• Kernel file ./drivers/firmware/xilinx/zynqmp.c, struct zynqmp_devinfo(9), struct pm_api_feature_data(9), zynqmp_pm_ret_code(9), do_fw_call_smc(9), do_fw_call_hvc(9), zynqmp_pm_feature(9), zynqmp_pm_is_function_supported(9), zynqmp_pm_invoke_fw_fn(9), zynqmp_pm_invoke_fn(9), zynqmp_pm_get_api_version(9), zynqmp_pm_get_chipid(9), zynqmp_pm_get_family_info(9), zynqmp_pm_get_sip_svc_version(9), zynqmp_pm_get_trustzone_version(9), get_set_conduit_method(9), zynqmp_pm_query_data(9)
• zynqmp_pm_clock_enable(9), zynqmp_pm_clock_disable(9), zynqmp_pm_clock_getstate(9), zynqmp_pm_clock_setdivider(9), zynqmp_pm_clock_getdivider(9), zynqmp_pm_clock_setparent(9), zynqmp_pm_clock_getparent(9), zynqmp_pm_set_pll_frac_mode(9), zynqmp_pm_get_pll_frac_mode(9), zynqmp_pm_set_pll_frac_data(9), zynqmp_pm_get_pll_frac_data(9), zynqmp_pm_set_sd_tapdelay(9), zynqmp_pm_sd_dll_reset(9), zynqmp_pm_ospi_mux_select(9)
• zynqmp_pm_write_ggs(9), zynqmp_pm_read_ggs(9), zynqmp_pm_write_pggs(9), zynqmp_pm_read_pggs(9), zynqmp_pm_set_boot_health_status(9), zynqmp_pm_reset_assert(9), zynqmp_pm_reset_get_status(9), zynqmp_pm_fpga_load(9), zynqmp_pm_fpga_get_status(9), zynqmp_pm_fpga_get_config_status(9), zynqmp_pm_pinctrl_request(9), zynqmp_pm_pinctrl_release(9), zynqmp_pm_pinctrl_set_function(9), zynqmp_pm_pinctrl_get_config(9), zynqmp_pm_pinctrl_set_config(9)
• zynqmp_pm_bootmode_read(9), zynqmp_pm_bootmode_write(9), zynqmp_pm_init_finalize(9), zynqmp_pm_set_suspend_mode(9), zynqmp_pm_request_node(9), zynqmp_pm_release_node(9), zynqmp_pm_get_rpu_mode(9), zynqmp_pm_set_rpu_mode(9), zynqmp_pm_set_tcm_config(9), zynqmp_pm_get_node_status(9), zynqmp_pm_force_pwrdwn(9), zynqmp_pm_request_wake(9), zynqmp_pm_start_rpu(9), zynqmp_pm_stop_rpu(9)
• zynqmp_pm_set_requirement(9), zynqmp_pm_load_pdi(9), zynqmp_pm_efuse_access(9), zynqmp_pm_register_notifier(9), zynqmp_pm_system_shutdown(9), zynqmp_pm_set_feature_config(9), zynqmp_pm_get_feature_config(9), zynqmp_pm_sec_read_reg(9), zynqmp_pm_sec_mask_write_reg(9), zynqmp_pm_set_sd_config(9), zynqmp_pm_set_gem_config(9), struct zynqmp_pm_shutdown_scope(9), zynqmp_pm_is_shutdown_scope_valid(9), zynqmp_clear_pm_state(9)

Source/version cutie: ./drivers/firmware/xilinx. Date stamp: October 2026. Page: zynqmp_pm_g..._node_status(9) in the Kernel API Manual. byeee bestie, go get that RPU node status 🫶✨