ice_dpll_txc..._on_dpll_get(9)

📦 version 7.3.1, in nixpkgs unstable

🎀 ice_dpll_txc..._on_dpll_get(9) — Kernel API Manual, bestie edition 💅

🌸 NAME

ice_dpll_txclk_state_on_dpll_get — get a state of Tx clk reference pin. That's the whole assignment, no cap. 💖

✨ SYNOPSIS

int ice_dpll_txclk_state_on_dpll_get (const struct dpll_pin *pin , void
       *pin_priv , const struct dpll_device *dpll , void *dpll_priv , enum
       dpll_pin_state *state , struct netlink_ext_ack *extack );

🫶 ARGUMENTS

  • pin — pointer to a pin 🎀
  • pin_priv — private data pointer passed on pin registration
  • dpll — registered dpll pointer
  • dpll_priv — private data pointer passed on dpll registration
  • state — on success holds pin state on parent pin
  • extack — error reporting

💖 DESCRIPTION

Okay so the tea: the TXCLK DPLL pin state is derived and not stored explicitly. It's giving calculated-on-the-spot energy, not saved-in-a-locker energy. 🧮✨

Only external TX reference clocks (SYNCE, EREF0) are modeled as DPLL pins. The internal ENET (TXCO) clock has no pin and, when selected, all TXCLK pins are reported DISCONNECTED. So when ENET is the moment, the TXCLK pin lineup says DISCONNECTED. 🫥

During a pending TXCLK switch, the requested pin may be reported as CONNECTED before hardware verification. That's the fine-print caveat, bestie — hardware acceptance and synchronization are reported exclusively via TXC DPLL lock-status. 👀🔒

🔐 CONTEXT

Acquires and releases pf->dplls.lock. Lock behavior: handled. 💅

🎯 RETURN

  • 0 — success
  • negative — failure

🌈 SEE ALSO

The whole link-up, and yes every single one made the list 💖

Sign-off szn, bestie: source/version ./drivers/net/ethernet/intel/ice, dated October 2026, page tag ice_dpll_txc..._on_dpll_get(9) — byeeeeee 💜🦋

📦 where this page comes from