zynqmp_pm_stop_rpu(9)
π zynqmp_pm_stop_rpu β stop that Cortex-R, bestie β¨
okay so real talk, this lil page lives in the Kernel API Manual (yes, that's the manual name, we're fancy now π ) and it's about telling the Real-time Processing Unit β that's the Cortex-R on the SoC, the little sibling core β to please sit down πͺπ
πΈ NAME πΈ
zynqmp_pm_stop_rpu β Stop Real-time Processing Unit (Cortex-R) on SoC
like, that's the whole vibe. RPU? stopped. Cortex-R? napping. the SoC is at peace β¨
π SYNOPSIS π
int zynqmp_pm_stop_rpu (const u32 node );
that's it. one argument. returns an int. she's lowkey minimal and I respect it π«Ά
π¦ ARGUMENTS π¦
nodeβ the power-domains id of the core π« (not a node in the "tree" sense, bestie, it's the power-domain identifier β the id you use to point at the core you're putting to sleep π΄)
π RETURN π
returns status β either success, or error+reason π (so if it flops it tells you why, which honestly? self-aware king behavior π)
ngl, always check the return value. no cap. a silent failure here means your RPU is out there living its truth while you think it's stopped π
π SEE ALSO π
okay this list is long long β grab a snack π β but every single one is here because the kernel file ./drivers/firmware/xilinx/zynqmp.c is a whole ecosystem, iykyk:
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_get_rpu_node_status(9),zynqmp_pm_force_pwrdwn(9),zynqmp_pm_request_wake(9),zynqmp_pm_start_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)
also the kernel file itself: ./drivers/firmware/xilinx/zynqmp.c β go read it, it's giving main character energy ππ₯
that's the whole page, bestie!! go stop that RPU, slay, and remember: check your return status π π§ββοΈ
cute lil sign-off: this masterpiece came from ./drivers/firmware/xilinx, dated October 2026 β archived in the Kernel API Manual forever and ever, mwah ππ
π¦ 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