zynqmp_pm_set_sd_tapdelay(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… zynqmp_pm_set_sd_tapdelay(9)

okay so welcome to the Kernel API Manual, bestie. Today's main character is zynqmp_pm_set_sd_tapdelay(9) β€” the little function that handles the tap delay for your SD device. No cap, it's giving very specific firmware business, and we're gonna read it together. πŸŽ€


🌸 NAME 🌸

zynqmp_pm_set_sd_tapdelay β€” Set tap delay for the SD device. That's the whole vibe: SD device, tap delay, set it. Slay. ✨

✨ SYNOPSIS ✨

int zynqmp_pm_set_sd_tapdelay (u32 node_id , u32 type , u32 value );

🫢 ARGUMENTS 🫢

  • node_id β€” Node ID of the device. Like, which device are we talking to? That's the one. πŸ‘‘
  • type β€” Type of tap delay to set (input/output). Input or output, pick your lane. πŸ’…
  • value β€” Value to set fot the tap delay. (The original really says "fot" β€” keeping the detail, bestie. 😭)

πŸ¦‹ DESCRIPTION πŸ¦‹

This function sets input/output tap delay for the SD device.

That's it. That's the whole description. It's lowkey short and highkey iconic. It does exactly what it says on the tin: input/output tap delay, SD device, done. πŸ’–

🌈 RETURN 🌈

Returns status, either success or error+reason.

So bestie, check that return value β€” success is the dream, and error+reason is the "why are we here" moment. Not me being dramatic, it's literally in the page. πŸ’€

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/firmware/xilinx/zynqmp.c β€” and the whole friend group: 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_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).


mwah πŸ’– this page is from ./drivers/firmware/xilinx, October 2026, and the manual page is zynqmp_pm_set_sd_tapdelay(9). Bye bestie, go set those tap delays! πŸŽ€βœ¨

πŸ“¦ where this page comes from