zynqmp_pm_set_tcm_config(9)
π zynqmp_pm_set_tcm_config β the kernel API manual, bestie edition
okay so this is a page from the Kernel API Manual and it's all about zynqmp_pm_set_tcm_config(9) β yes that's a mouthful, we're saying it with our whole chest π«Ά
β¨ NAME β¨
zynqmp_pm_set_tcm_config β configure TCM, that's literally the whole job π
πΈ SYNOPSIS πΈ
int zynqmp_pm_set_tcm_config (u32 node_id , enum rpu_tcm_comb tcm_mode
);
like, that's the shape of it. it returns an int, it takes two things, we move π
π¦ ARGUMENTS π¦
node_idβ the Firmware specific TCM subsystem ID. it's the ID the firmware knows this TCM subsystem by, no cap πͺͺtcm_modeβ the Argument 1 you pass to the requested IOCTL call, eitherPM_RPU_TCM_COMBorPM_RPU_TCM_SPLIT. pick one, bestie, those are the two vibes βοΈ
π DESCRIPTION π
so what does this function do? it's used to set the RPU mode to split or combined. that's it, that's the tea β two modes, one function, main character energy honestly π
π₯ RETURN π₯
status: 0 for success, else failure. so if you get a 0 you ate, and if you don'tβ¦ you did not eat ππ
π SEE ALSO π
the friend group is huge, buckle up babes, everyone's invited π«Ά
- 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_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 I said. everyone. every single one. we don't gatekeep here π
okay that's the whole page bestie, and real quick the cute little sign-off from the source at the bottom said ./drivers/firmware/xilinx with October 2026 on it, so yeah β that's where this came from and when it was dated π
β¨ 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