zl3073x_dpll...cted_ref_get(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME 💅

zl3073x_dpll_connected_ref_get — bestie, this one gets the reference that's currently connected ✨

Ok so real quick, before we dive in — this page is from the Kernel API Manual, section 9, and it's the zl3073x_dpll_connected_ref_get(9) page. Grab a snack, we're doing kernel DPLL stuff 🎀

✨ SYNOPSIS ✨

u8 zl3073x_dpll_connected_ref_get (struct zl3073x_dpll *zldpll );

🫶 ARGUMENTS 🫶

  • zldpll — a pointer to zl3073x_dpll. That's the DPLL object we're snooping on 💜

🌸 DESCRIPTION 🌸

So what does it actually do? It goes looking for the reference that's currently connected — like, the one your DPLL is actually locked to right now. The way it just... finds the current boo 😭 Main character energy fr fr.

👑 RETURN 👑

It hands you back the reference index if the DPLL is locked — slay 💅

Otherwise? You get ZL3073X_DPLL_REF_NONE, which is the "nobody's home" answer, no cap.

🦋 SEE ALSO 🦋

Everything's in the kernel file ./drivers/dpll/zl3073x/dpll.c, and here's the whole friend group 👇

That's the whole page bestie!! 💖 This one lives over in ./drivers/dpll/zl3073x, and it's dated October 2026 — so yeah, mark your calendar, future girlies 🗓️✨ Go get that connected reference, you've got this 🫶💅

📦 where this page comes from