STRUCT MVEBU_CP110_UTMI(9)

💅 struct mvebu_cp110_utmi(9) — like, the Kernel API Manual moment

okay bestie, gather round, because today we're meeting struct mvebu_cp110_utmi, and she is literally the PHY driver data of the group chat. No cap. This is straight out of the Kernel API Manual, and honestly? iconic.

---

✨ NAME ✨

struct mvebu_cp110_utmi — PHY driver data. that's her whole job description, she's booked and busy 🎀

---

🌸 SYNOPSIS 🌸

here's the whole fit, bestie, look at her:

struct mvebu_cp110_utmi {
    void __iomem *regs;
    struct regmap *syscon;
    struct device *dev;
    const struct phy_ops *ops;
 };

four members, zero filler, main character energy only 🔥

---

🦋 Members 🦋

okay let's do the roll call, one by one, because every single field matters, fr fr:

• regs — PHY registers. this is where the PHY keeps its stuff, the literal void __iomem * of it all 💫
• syscon — Regmap with system controller registers. sis is holding the regmap for the system controller registers, and she's slaying it 🫶
• dev — device driver handle. the device driver's whole handle, right there, a whole struct device * 💖
• ops — phy ops. the const struct phy_ops * queen herself, keeping it const so nobody touches her vibe ✨

bestie note: those are pointers into void __iomem, struct regmap, struct device, and const struct phy_ops — no new types invented, no details dropped, we stay factual in this house 💅

---

👑 SEE ALSO 👑

go look at your other faves, they're in the group chat too:

• Kernel file ./drivers/phy/marvell/phy-mvebu-cp110-utmi.c — the actual source file where this all lives
• struct mvebu_cp110_utmi_port(9) — her sibling, also a whole manpage, also worth the read 💀

---

and that's the page! 🧚 sign-off time: this whole thing is sourced from ./drivers/phy/marvell, dated October 2026, and it's filed under struct mvebu_cp110_utmi(9). go off, bestie, you understood the assignment 💜