STRUCT MVEBU_A3700_UTMI_CAPS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, this is struct mvebu_a3700_utmi_caps(9) from the Kernel API Manual, and it is literally the little info card for PHY capabilities. πŸ’…

✨ NAME ✨

struct mvebu_a3700_utmi_caps β€” PHY capabilities. That’s the whole vibe, no cap. πŸ¦‹

🌈 SYNOPSIS 🌈

       struct mvebu_a3700_utmi_caps {
           int usb32;
           const struct phy_ops *ops;
        };

🌸 Members 🌸

  • usb32 β€” a flag indicating which PHY is in use, and bestie, it impacts the register map. The options it’s pointing at are:
    • The UTMI PHY wired to the USB3/USB2 controller (otg)
    • The UTMI PHY wired to the USB2 controller (host only)
  • ops β€” PHY operations. That’s it, that’s the member. 🫢

πŸ’œ SEE ALSO πŸ’œ

  • Kernel file ./drivers/phy/marvell/phy-mvebu-a3700-utmi.c struct mvebu_a3700_utmi(9)

byeee πŸ’– this page comes from ./drivers/phy/marvell, dated October 2026, and the footer label is struct mvebu...00_utmi_caps(9) β€” periodt. πŸŽ€

πŸ“¦ where this page comes from