STRUCT ZYNQMP_PM_SHUTDOWN_SCOPE(9)
π NAME π
struct zynqmp_pm_shutdown_scope β the struct for a shutdown scope, bestie β¨
okay so real quick, before we even get into it: this page is from the Kernel API Manual, section 9, and it's all about struct zynqmp_pm_shutdown_scope(9). Buckle up, there's literally one struct and it's lowkey iconic π
β¨ SYNOPSIS β¨
struct zynqmp_pm_shutdown_scope {
const enum zynqmp_pm_shutdown_subtype subtype;
const char *name;
};
that's the whole thing. two members. clean. minimal. giving main character energy fr fr π
π MEMBERS π
subtypeβ the shutdown subtype, so you know what kind of shutdown we're talking about here πnameβ the matching string for thescopeargument, aka the little name tag that lets the scope get matched up π·οΈ
π¦ DESCRIPTION π¦
so what does this bad boy actually do? it encapsulates the mapping between a shutdown scope ID and its string πΈ
like, it's the lil translator. the glow-up between "number" and "word". the ID says one thing, the string says another, and this struct is the bestie that holds both so they never get separated π
ngl it's a tiny struct but it's doing genuine emotional labour. respect her.
π SEE ALSO π
bestie, this list is long and I'm not skipping a single one of them β every single one of these is a real reference and you're gonna get all of them, no cap πβ¨
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_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)zynqmp_pm_is_shutdown_scope_valid(9)zynqmp_clear_pm_state(9)
like I said. every single one. ate and left no crumbs π
and that's the whole vibe check, bestie β go read the source, slay your day, and remember: ./drivers/firmware/xilinx, Kernel API Manual, October 2026. 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