zl3073x_ref_freq_meas_latch(9)
β¨ NAME β¨
zl3073x_ref_freq_meas_latchβ latch reference frequency measurements π
π SYNOPSIS π
This is the Kernel API Manual, page zl3073x_ref_freq_meas_latch(9), bestie β welcome to the function-signature moment π«Ά Here it is, exactly:
int zl3073x_ref_freq_meas_latch (struct zl3073x_dev *zldev , u8 type );
π ARGUMENTS π
zldevβ pointer tozl3073x_devstructure π¦typeβ measurement type, specifically theZL_REF_FREQ_MEAS_CTRL_*kind π
π¦ DESCRIPTION π¦
Okay so the vibe of this function is: it waits for the previous measurement to finish first β like, it will not let the old one overlap, periodt β then it selects all references, and then it requests a new measurement of the given type. That's the whole flow, and honestly? It ate. β¨
πΈ RETURN πΈ
It returns 0 on success, and <0 on error π So yeah: 0 is the slay outcome, negative is the crying-in-the-group-chat outcome.
π₯ SEE ALSO π₯
Kernel file ./drivers/dpll/zl3073x/core.c β and the whole linked function squad is:
zl3073x_read_u8(9)zl3073x_write_u8(9)zl3073x_read_u16(9)zl3073x_write_u16(9)zl3073x_read_u32(9)zl3073x_write_u32(9)zl3073x_read_u48(9)zl3073x_write_u48(9)zl3073x_poll_zero_u8(9)zl3073x_do_hwreg_op(9)zl3073x_read_hwreg(9)zl3073x_write_hwreg(9)zl3073x_update_hwreg(9)zl3073x_write_hwreg_seq(9)zl3073x_ref_phase_offsets_update(9)zl3073x_ref_freq_meas_update(9)zl3073x_dev_phase_meas_setup(9)zl3073x_dev_start(9)zl3073x_dev_stop(9)zl3073x_dev_probe(9)
xoxo, from the ./drivers/dpll/zl3073x source/version, dated October 2026, on page zl3073x_ref_freq_meas_latch(9) πβ¨π
π¦ 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