fwnode_graph..._remote_port(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

fwnode_graph_get_remote_port β€” returns the fwnode of a remote port, bestie ✨

(Also hi, welcome, this is a page from the Kernel API Manual, section 9 πŸŽ€)


🌸 SYNOPSIS 🌸

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

πŸ¦‹ ARGUMENTS πŸ¦‹

  • fwnode β€” an endpoint firmware node that's pointing at the remote endpoint 🫢

✨ DESCRIPTION ✨

Okay so what this does: it extracts the firmware node of a remote port β€” the one your fwnode is pointing to. That's the whole vibe. It gives you the remote port's fwnode, no cap πŸ’…

🚨 The caller is responsible for calling fwnode_handle_put on the returned fwnode pointer. This is not a drill, bestie β€” you got the pointer, you clean it up. Not me doing it for you 😭

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/base/property.c β€” and honestly, the whole friend group showed up, so here's the full rollout πŸ‘‘


πŸ’œ okay that's the page, ily, go call fwnode_handle_put πŸ’œ

This little icon was served fresh from ./drivers/base, dated October 2026, and it lives under the name fwnode_graph..._remote_port(9) πŸŽ€ πŸ¦‹ ⭐

πŸ“¦ where this page comes from