zl3073x_dev_out_dpll_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… zl3073x_dev_out_dpll_get πŸ’…

Okay so bestie, you found a page from the Kernel API Manual β€” this one's all about zl3073x_dev_out_dpll_get, and honestly? It's a little one-trick pony but it eats. Let's get into it ✨


🌸 NAME 🌸

zl3073x_dev_out_dpll_get β€” get the DPLL ID that a given output is being driven by πŸŽ€

Like, you point at an output, and it tells you which DPLL is out there holding its hand. Cute, right?


✨ SYNOPSIS ✨

u8 zl3073x_dev_out_dpll_get (struct zl3073x_dev *zldev , u8 index );

That's it. Two args, one tiny u8 coming back atcha. No cap. πŸ¦‹


🫢 ARGUMENTS 🫢

  • zldev β€” pointer to the zl3073x device. Yep, the whole device struct. You need the main character here, not just a piece of it πŸ‘‘
  • index β€” the output index. Which output are we talking about? Tell her. πŸ”₯

⭐ RETURN ⭐

It hands you back the ID of the DPLL that the given output is driven by πŸ’–

That's the whole vibe β€” an ID, that's the answer, periodt.


🧚 SEE ALSO 🧚

The kernel file lives at ./drivers/dpll/zl3073x/core.h β€” go say hi 🌈

And here's the whole friend group, no one left out:

Lowkey a whole squad πŸ’€ Go read them all, iykyk.


Real talk though β€” this page lives under ./drivers/dpll/zl3073x and it's dated October 2026, so like… future vibes fr fr πŸ™ˆ

Okay bye bestie, go get that DPLL ID β€” slay πŸ’œπŸŽ€βœ¨

πŸ“¦ where this page comes from