devm_of_phy_get(9)

🦋 devm_of_phy_get(9) — Kernel API Manual

okay bestie, welcome to the Kernel API Manual page for devm_of_phy_get(9) — this is the one where we look up a phy and obtain a reference to it. no cap, the devm girlies are gonna eat. 💅

✨ NAME ✨

devm_of_phy_get — lookup and obtain a reference to a phy. 🎀

🌸 SYNOPSIS 🌸

struct phy * devm_of_phy_get (struct device *dev , struct device_node
       *np , const char *con_id );

🫶 ARGUMENTS 🫶

• dev — the device that requests this phy.
• np — the node containing the phy.
• con_id — the name of the phy from the device's point of view.

💖 DESCRIPTION 💖

So here's the vibe, bestie: it gets the phy using of_phy_get, and then associates a device with it using devres. ✨

On driver detach, the release function is invoked on the devres data, and then the devres data is freed. That's the whole little lifecycle — iconic, honestly. 💅

🔥 SEE ALSO 🔥

The kernel file is ./drivers/phy/phy-core.c — go peek at it for the full lore. 👑

• phy_create_lookup(9)
• phy_remove_lookup(9)
• phy_init(9)
• phy_exit(9)
• phy_power_on(9)
• phy_power_off(9)
• phy_calibrate(9)
• phy_notify_connect(9)
• phy_notify_disconnect(9)
• phy_notify_state(9)
• phy_configure(9)
• phy_validate(9)
• _of_phy_get(9)
• of_phy_get(9)
• of_phy_put(9)
• phy_put(9)
• devm_phy_put(9)
• of_phy_simple_xlate(9)
• phy_get(9)
• devm_phy_get(9)
• devm_phy_optional_get(9)
• devm_of_phy_optional_get(9)
• devm_of_phy_get_by_index(9)
• phy_create(9)
• devm_phy_create(9)
• phy_destroy(9)
• devm_phy_destroy(9)
• __of_phy_provider_register(9)
• __devm_of_phy_provider_register(9)
• of_phy_provider_unregister(9)
• devm_of_phy_provider_unregister(9)
• phy_release(9)

./drivers/phy · October 2026 · devm_of_phy_get(9) — that's the source/version and date, bestie. byeee, go get that phy reference 💜🌈