zynqmp_pm_get_node_status(9)
π
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:
- 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_rpu_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)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms