ice_txclk_enable_peer(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ice_txclk_enable_peer β€” bestie edition

ok so this is a page from the Kernel API Manual, and we're talking about ice_txclk_enable_peer(9). Strap in, it's actually not that deep, i promise 🫢


✨ NAME ✨

ice_txclk_enable_peer β€” literally just enables the required TX reference clock on the peer PHY. that's the whole vibe. πŸŽ€


🌸 SYNOPSIS 🌸

int ice_txclk_enable_peer (struct ice_pf *pf , enum ice_e825c_ref_clk
clk );

like yes, that's the whole signature, no cap ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • pf β€” pointer to the PF structure. just a pointer, she's pointing at stuff, iconic behavior πŸ’…
  • clk β€” the TX reference clock that must be enabled. this is the one we're turning on, main character energy frfr πŸ‘‘

πŸ’– DESCRIPTION πŸ’–

okay so listen. some TX reference clocks on E825-class devices (we're talking SyncE and EREF0 here) have to be enabled on both PHY complexes so that routing actually works properly. it's giving teamwork, it's giving "we do this together or not at all" 😭

the rules, and yes there are rules:

  • SyncE must be enabled on both PHYs when it's used by PHY0 🌈
  • EREF0 must be enabled on both PHYs when it's used by PHY1 ⭐

so if the requested clock isn't enabled on the peer PHY yet, we enable it. simple as that. slay. πŸ’…

heads up bestie: ENET does not require duplication, so it gets ignored. don't come for it, it's just living its life πŸ™ˆ

πŸ”₯ RETURN πŸ”₯

  • 0 on success πŸŽ‰
  • negative error code on failure 😭 (she tried her best)

🧚 SEE ALSO 🧚

like, go read those too, they're all part of the same friend group fr fr πŸ’œ


ok that's the whole page!! πŸ’– this gem lives in ./drivers/net/ethernet/intel/ice, dated October 2026, and the manual credits it as ice_txclk_enable_peer(9). periodt. βœ¨πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from