devm_usb_get_phy_by_phandle(9)

📦 version 7.3.1, in nixpkgs unstable

💖 devm_usb_get_phy_by_phandle(9) 💖

okay so bestie, welcome to the Kernel API Manual — this one's all about devm_usb_get_phy_by_phandle, and it's genuinely so useful, let me tell you everything ✨

✨ NAME ✨

devm_usb_get_phy_by_phandle — find the USB PHY by phandle 🎀

🦋 SYNOPSIS 🦋

struct usb_phy * devm_usb_get_phy_by_phandle (struct device *dev , const
char *phandle , u8 index );

🌸 ARGUMENTS 🌸

  • dev — the device that's requesting this phy, like it's the one doing the asking 💅
  • phandle — the name of the property that's holding the phy phandle value, iykyk
  • index — the index of the phy, yes there can be a whole lineup 🫶

🔥 DESCRIPTION 🔥

So here's the vibe: this returns the phy driver that's associated with the given phandle value, after getting a refcount to it. Iconic. But also — it returns -ENODEV if there's no such phy, or -EPROBE_DEFER if there is a phandle to the phy but the device isn't loaded yet. Not me being dramatic, that's literally the deal 😭

While it's at it, it also associates the device with the phy using devres. And on driver detach? The release function is invoked on the devres data, then the devres data is freed. Cleanup queen behavior, honestly 👑

For use by USB host and peripheral drivers. That's the whole audience, no gatekeeping.

💜 SEE ALSO 💜

Kernel file ./drivers/usb/phy/phy.c plus the whole friend group:

ngl bestie, always check your return value — -ENODEV and -EPROBE_DEFER are two very different moods and you don't wanna mix them up 🙈

okay that's the whole page, mwah 💋 — this gem lives in ./drivers/usb/phy, dated October 2026, and it's called devm_usb_get_phy_by_phandle(9) in case you forgot already. slay, go write some drivers 🧚‍♀️💖

📦 where this page comes from