fwnode_get_phy_node(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– fwnode_get_phy_node(9) πŸ’–

okay so real talk, this is a page from the Kernel API Manual and it's literally about grabbing a phy_node off a fwnode β€” bestie, it's giving "small function, huge friend group". let's get into it 🫢


✨ NAME ✨

fwnode_get_phy_node β€” get the phy_node using the named reference. that's it, that's the whole job πŸ’…


🌸 SYNOPSIS 🌸

struct fwnode_handle * fwnode_get_phy_node (const struct fwnode_handle
*fwnode );

look at her go 😭 returns a struct fwnode_handle *, takes a const struct fwnode_handle *. iconic signature behavior, no notes.


πŸŽ€ ARGUMENTS πŸŽ€

  • fwnode β€” pointer to the fwnode from which phy_node has to be obtained. yes literally just hand her the fwnode and she'll go get the phy_node for you, she's so nice like that πŸ’œ

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so for what actually comes back, go peek at the return conditions of fwnode_find_reference β€” that's where the real lore lives, iykyk ✨

now the spicy part πŸ”₯ For ACPI, only "phy-handle" is supported. like, that's the whole menu, one item, no substitutions. The legacy DT properties "phy" and "phy-device" are not supported in ACPI β€” nope, not happening, don't even try it bestie πŸ™ˆ

DT, on the other hand, is the main character and supports all three of the named references to the phy node: "phy", "phy-device", and "phy-handle". she ate πŸ‘‘


⭐ SEE ALSO ⭐

Kernel file ./drivers/net/phy/phy_device.c β€” and then the whole squad, fr fr:

like... the whole net/phy friend group showed up to the party πŸ˜­πŸ’€


that's the page bestie!! 🧚 she lives in ./drivers/net/phy, version dated October 2026, and she's still fwnode_get_phy_node(9) at the end of the day. mwah πŸ’‹ go get that phy_node, you got this πŸ’–βœ¨πŸ“

πŸ“¦ where this page comes from