zynqmp_pm_reset_assert(9)
π
zynqmp_pm_reset_assert(9) β Kernel API Manual β¨
okay bestie, so you're in the Kernel API Manual and we're about to talk about one little function that flips a reset line like it's a light switch. it's giving "tiny function, real consequences" and honestly? iconic. let's get into it π«Ά
πΈ NAME πΈ
zynqmp_pm_reset_assert β bestie it literally requests the setting of a reset: 1 means assert it, 0 means release it. that's the whole vibe check right there π
π¦ SYNOPSIS π¦
int zynqmp_pm_reset_assert (const u32 reset , const enum
zynqmp_pm_reset_action assert_flag );
yes she's a whole int return, yes she takes two args, no she is not going to elaborate further, that's what ARGUMENTS is for π
β¨ ARGUMENTS β¨
resetβ the reset you wanna configure. pick your reset, girl, this is the one πassert_flagβ the flag stating whether the reset should be asserted (1) or released (0). that's it. onesie or zerosie, no in-between π
π RETURN π
Returns status β either success or error+reason. so like, she'll tell you if it worked, and if it didn't she'll tell you why, which is more than some people in your life will do ππ«Ά
π§ SEE ALSO π§
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_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)
like, the whole friend group showed up for this one β no cap, that's a lot of see-also's and every single one of them matters π
and that's the page, bestie π go assert (or release) responsibly π
source file lives in ./drivers/firmware/xilinx, dated October 2026 β mwah, catch you on the next manpage ππΈ
π¦ 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