STRUCT XPSGTR_PHY(9)

💅 struct xpsgtr_phy(9) — like, the whole kernel API manual moment

okay so bestie, welcome to struct xpsgtr_phy(9) ✨ this is the man page for the lane struct, straight out of the Kernel API Manual, and honestly? it ate. let's get into it 🫶

---

✨ NAME ✨

struct xpsgtr_phy — representation of a lane 💫

that's it. that's the whole vibe. one struct, one lane, main character energy 👑

---

🌸 SYNOPSIS 🌸

struct xpsgtr_phy {
    struct phy *phy;
    u8 instance;
    u8 lane;
    u8 protocol;
    bool skip_phy_init;
    struct xpsgtr_dev *dev;
    unsigned int refclk;
 };

no cap, that's the entire struct — copy it exactly, don't be out here renaming fields, i'm watching 👀 (affectionately)

---

🎀 Members 🎀

time for the member-by-member vibe check, let's go 🔥

• phy — a pointer to the kernel PHY device. literally just a lil pointer bestie, nothing more, nothing less 💖
• instance — the instance of the protocol type. think: the lane within a protocol, or the USB/Ethernet controller. it's giving "which one of you is it" 🌈
• lane — the lane number. yes. that's the whole thing. iconic brevity 💅
• protocol — the protocol that this lane operates in. slay, know your lane's context 🦋
• skip_phy_init — if this is true, skip phy_init. simple as. 🙈
• dev — a pointer to the xpsgtr_dev instance. say hi to the parent 🫶
• refclk — the reference clock index. number go brrr ⏰

okay but fr fr, keep those field names exactly as written — they're <pink>literal</pink>, not a suggestion 💀

---

👑 SEE ALSO 👑

the whole friend group 🧚 — they all live in the kernel file ./drivers/phy/xilinx/phy-zynqmp.c:

• struct xpsgtr_ssc(9)
• struct xpsgtr_dev(9)
• xpsgtr_save_lane_regs(9)
• xpsgtr_restore_lane_regs(9)
• xpsgtr_bypass_scrambler_8b10b(9)

go read them, iykyk 💜

---

and that's the page!! mwah 😭💖 this lil beauty lives in ./drivers/phy/xilinx and it's dated October 2026 — so go forth, read your lane struct, and remember: every single member above is doing its job so you don't have to ⭐🍓