zynqmp_pm_register_notifier(9)
π zynqmp_pm_register_notifier(9) π
okay bestie so this is a page straight out of the Kernel API Manual and it's all about zynqmp_pm_register_notifier β the PM API that lets a subsystem sign itself up to get pinged about one specific event/error. β¨
πΈ NAME πΈ
zynqmp_pm_register_notifier β the PM API for registering a subsystem so it gets notified about a specific event/error. literally its whole personality. π«Ά
π SYNOPSIS π
int zynqmp_pm_register_notifier (const u32 node , const u32 event ,
const u32 wake , const u32 enable );
β ARGUMENTS β
nodeβ the Node ID that this event is related to. the main character of the pairing, iykyk πeventβ the Event Mask of the Error events you want to get notified about. pick your faves π―wakeβ wake the subsystem up when it catches the event β set it to1for that π€β‘οΈπ₯enableβ1turns the registration on,0turns it off. the on/off switch, no cap π
π¦ DESCRIPTION π¦
so what does it actually do? this function is how you register β or un-register β a particular node-event combination in firmware. that's it, that's the vibe. π
β¨ RETURN β¨
returns a status β either success, or error + reason. so yeah, check it, don't just assume it slayed π
π SEE ALSO π
the whole friend group, fr fr β plus the 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_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_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)
and that's the whole page, bestie!! π this little gem lives over in ./drivers/firmware/xilinx, dated October 2026, and it's filed under zynqmp_pm_register_notifier(9). go forth and get notified π¦β¨
π¦ 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