STRUCT MVEBU_CP110_UTMI_PORT(9)

🌸 NAME 🌸

struct mvebu_cp110_utmi_port — it's giving PHY port data, bestie 💅 this is the little struct that holds the deets for one UTMI port, and it lives in the Kernel API Manual (yes that's the manual name, we're fancy like that ✨).

🦋 SYNOPSIS 🦋

ok so picture this, the whole struct, no cap, exactly like this:

struct mvebu_cp110_utmi_port {
    struct mvebu_cp110_utmi *priv;
    u32 id;
    enum usb_dr_mode dr_mode;
    bool swap_dx;
};

that's it, that's the vibe 🎀 four fields, zero drama.

💖 MEMBERS 💖

• priv — the PHY driver data 🫶 literally the hookup to the driver's own stuff, main character energy.
• id — the PHY port ID ✨ which port are we even talking about, bestie, this is how you know.
• dr_mode — the PHY connection, and it's one of exactly two moods: USB_DR_MODE_HOST or USB_DR_MODE_PERIPHERAL 👑 pick your fighter.
• swap_dx — a bool that says whether to swap d+/d- signals 🙈 like, are we flipping the wires or not, that's the whole question.

lowkey important: that's d+ and d-, the actual signal lines, not a typo, not a vibe, fr fr 💀

🔥 SEE ALSO 🔥

• Kernel file ./drivers/phy/marvell/phy-mvebu-cp110-utmi.c 📁 like, go read the source, it ate.
• struct mvebu_cp110_utmi(9) — the sibling struct, iconic, they come as a set 💜

ok that's the whole page, you're officially educated 💅 this was brought to you by the fine people over at ./drivers/phy/marvell 🌈, dated October 2026 ⭐, and yes the manual is the Kernel API Manual in case you forgot already 😭 go forth and configure ports, bestie, you got this 🧚‍♀️💖