STRUCT MTK_XFI_TPHY(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct mtk_xfi_tphy(9) β€” the Kernel API Manual glow-up πŸŽ€

okay so bestie, welcome to the struct mtk_xfi_tphy(9) page from the Kernel API Manual ✨ this is the run-time data of the XFI phy instance, and we're gonna get into every single little field, no cap πŸ’…


🌸 NAME 🌸

struct mtk_xfi_tphy β€” run-time data of the XFI phy instance πŸ¦‹


✨ SYNOPSIS ✨

struct mtk_xfi_tphy {
    void __iomem            *base;
    struct device           *dev;
    struct reset_control    *reset;
    struct clk_bulk_data    clocks[MTK_XFI_TPHY_NUM_CLOCKS];
    bool da_war;
 };

πŸ‘‘ Members πŸ‘‘

  • base β€” the IO memory area used to access the phy registers. it's giving "where the actual hardware lives" energy πŸ”₯
  • dev β€” the kernel device used to output prefixed debug info. lowkey your debug messages' main character πŸ’œ
  • reset β€” the reset control corresponding to the phy instance. when this phy needs a little reset moment, this is the hookup πŸŽ€
  • clocks β€” all clocks required for the phy to operate. yes, all of them, and there are MTK_XFI_TPHY_NUM_CLOCKS of them, periodt ⭐
  • da_war β€” enables work-around for 10GBase-R mode. it's literally right there in the name, bestie 🫢

πŸ¦‹ SEE ALSO πŸ¦‹


and that's the whole vibe check, bestie πŸ’– this page comes from ./drivers/phy/mediatek, dated October 2026, and it's literally titled struct mtk_xfi_tphy(9) β€” slay, go read the source, iykyk πŸŒˆπŸ’…

πŸ“¦ where this page comes from