__phy_package_write_mmd(9)

💅 NAME 💅

__phy_package_write_mmd — bestie, this is the "write an MMD register, but relative to the PHY package base addr" girlie ✨

---

🦋 SYNOPSIS 🦋

int __phy_package_write_mmd (struct phy_device *phydev , unsigned int
addr_offset , int devad , u32 regnum , u16 val );

---

🎀 ARGUMENTS 🎀

• phydev — the phy_device struct, aka the whole main character of this operation 💖
• addr_offset — the offset that gets added to the PHY package base_addr, lowkey the glue holding this together 🫶
• devad — the MMD you're writing to, pick your fave 👑
• regnum — the register on that MMD you're writing to, like the exact door number 🚪
• val — the value you're writing into regnum, the actual gift inside the box 🎁

---

🌸 DESCRIPTION 🌸

okay so this is a convenience helper for writing a register of an MMD on a given PHY using the PHY package base address. The base address is literally added to the addr_offset value — no cap, that's the whole trick ✨

Same calling rules as for __phy_write — fr fr, don't reinvent the rules, just follow hers 💅

---

💀 NOTE 💀

It's assumed that the entire PHY package is either C22 or C45. Not a mix, not a vibe mash-up — pick one, periodt 🚫🌈

---

🔥 SEE ALSO 🔥

Kernel file ./drivers/net/phy/phy_package.c

• struct phy_package_shared(9)
• phy_package_lock(9)
• phy_package_unlock(9)
• __phy_package_read_mmd(9)
• phy_package_join(9)
• of_phy_package_join(9)
• phy_package_leave(9)
• devm_phy_package_join(9)
• devm_of_phy_package_join(9)

go read the whole friend group, they all slay in their own way 🧚💜

---

k bye bestie, this page lives in ./drivers/net/phy, stamped October 2026, and it's literally called __phy_package_write_mmd(9) — iykyk 💖✨