of_phy_package_join(9)

okay so bestie, welcome to the of_phy_package_join(9) page from the Kernel API Manual 💖 this one is literally about joining a common PHY group in a PHY package, and it’s giving “group chat but make it PHY” energy 🎀.

🎀 NAME 🎀

of_phy_package_join — join a common PHY group in PHY package

✨ SYNOPSIS ✨

int of_phy_package_join (struct phy_device *phydev , size_t priv_size );

🫶 ARGUMENTS 🫶

• phydev — target phy_device struct
• priv_size — if non-zero allocate this amount of bytes for private data

🌸 DESCRIPTION 🌸

okay so here’s the tea ☕ this is a variant of phy_package_join for a PHY package defined in DT.

The parent node of the phydev is checked as a valid PHY package node structure — by matching the node name "ethernet-phy-package" — and the base_addr for the PHY package is passed to phy_package_join. no cap, that’s the whole vibe check 🔥

With this configuration the shared struct will also have the np value filled to use additional DT defined properties in PHY specific probe_once and config_init_once PHY package OPs. slay ✨

Returns < 0 on error, 0 on success. Esp. calling phy_package_join with the same cookie but a different priv_size is an error. Or a parent node is not detected or is not valid or doesn’t match the expected node name for PHY package. 😭 like, those are the error girlies, fr fr.

🦋 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_write_mmd(9)
• phy_package_join(9)
• phy_package_leave(9)
• devm_phy_package_join(9)
• devm_of_phy_package_join(9)

mwah 💋 source/version line: ./drivers/net/phy; date: October 2026; page: of_phy_package_join(9) — periodt. 🎀