zynqmp_pm_g...zone_version(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ zynqmp_pm_get_trustzone_version β€” Kernel API Manual πŸ¦‹

okay so real talk, the page title up top got literally chopped into zynqmp_pm_g...zone_version(9) and honestly? mysterious. icon behavior. but the full name is down in NAME and we're gonna get into it. this one's from the Kernel API Manual, and it is such a little function. let's go πŸ’…


✨ NAME ✨

zynqmp_pm_get_trustzone_version β€” Get secure trustzone firmware version πŸŽ€

like, that's it. that's the whole vibe. she fetches the version of the secure trustzone firmware. no cap.


🌈 SYNOPSIS 🌈

int zynqmp_pm_get_trustzone_version (u32 *version );

look at her. one argument. returns an int. clean, minimal, main character energy fr fr.


πŸ’– ARGUMENTS πŸ’–

  • version β€” Returned version value ✨ β€” this is where the version comes back out, so you gotta hand her a pointer to a u32 and she'll fill it in. she's not asking, she's telling (politely).

πŸ”₯ RETURN πŸ”₯

Returns status, either success or error+reason πŸ’€ β€” so yeah, check that return value, bestie. success is success, and error comes with a reason attached. not me ignoring a return code… couldn't be me πŸ™ˆ


πŸ‘‘ SEE ALSO πŸ‘‘

okay this is the part where the page just. goes off. there's a whole friend group and every single one of them is invited to the function. also the kernel file lives at ./drivers/firmware/xilinx/zynqmp.c πŸ¦‹

the whole squad, in order, no one left out:

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), 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_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)

the way that list just keeps going 😭 she said "and my friends" and brought the entire kernel. iykyk.


and that's the page!! 🫢 sourced straight from ./drivers/firmware/xilinx, dated October 2026, and the title up top still reads zynqmp_pm_g...zone_version(9) because we love a dramatic abbreviation. periodt. πŸ’œ

πŸ“¦ where this page comes from