ice_dpll_lock_status_get(9)

📦 version 7.3.1, in nixpkgs unstable

💅 ice_dpll_lock_status_get(9) — the Kernel API Manual glow-up 🎀

okay bestie, so this one is from the Kernel API Manual (yes, that's the manual name, we're fancy now ✨) and it's about ice_dpll_lock_status_get — the dpll lock status callback. let's get into it 🦋

✨ NAME ✨

ice_dpll_lock_status_get — get dpll lock status callback. that's it, that's the whole vibe. 💖

🫶 SYNOPSIS 🫶

int ice_dpll_lock_status_get (const struct dpll_device *dpll , void
*dpll_priv , enum dpll_lock_status *status , enum dpll_lock_status_error
*status_error , struct netlink_ext_ack *extack );

no cap, that's the exact signature. don't be retyping it by hand, copy-paste is self care 🙈

🌸 ARGUMENTS 🌸

  • dpll — registered dpll pointer. the main character of this whole function, honestly 👑
  • dpll_priv — private data pointer passed on dpll registration. the lil backpack of secrets it brought along 🎀
  • status — on success holds dpll's lock status. this is where the good news lands ✨
  • status_error — status error value. yep, the error branch gets its own lil slot 💀
  • extack — error reporting. the messenger that snitches to netlink when something goes wrong 🫶

🦋 DESCRIPTION 🦋

so this is a Dpll subsystem callback — it provides dpll's lock status. it's giving "the dpll subsystem asked me a question and I'm the one who knows the answer." periodt. 💅

🔥 CONTEXT 🔥

heads up babe: this one acquires pf->dplls.lock. it's a lock. respect the lock. 😭

⭐ RETURN ⭐

  • 0 — success 🎉 slay
  • negative — failure 💀 not slay, but the vibes are still informative

💜 SEE ALSO 💜

okay this list is long, and when I say long I mean long — but every single one is here, bestie. iykyk 🧚

🎀 okay that's the whole page, bye bestie 🎀

this lil masterpiece lives in ./drivers/net/ethernet/intel/ice and it's stamped October 2026 — so yes, it's from the future, and yes, it ate. 💅🔥 no cap, go read some more kernel docs, ily 🫶

📦 where this page comes from