fwnode_grap..._port_parent(9)

💅 fwnode_grap..._port_parent(9) — from the Kernel API Manual, bestie 🎀

Okay so listen, this one lives in the Kernel API Manual and it's actually such a vibe once you get it. Buckle up 🦋

---

✨ NAME ✨

fwnode_graph_get_remote_port_parent — literally returns the fwnode of a remote device. That's the whole gig. 👑

---

🌸 SYNOPSIS 🌸

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

Like, look at her. She takes one const struct fwnode_handle * and hands you back a struct fwnode_handle *. Main character energy fr fr. ✨

---

🫶 ARGUMENTS 🫶

• fwnode — the endpoint firmware node that's pointing at the remote endpoint. She's the one doing the pointing, not the one being pointed at, iykyk. 🎯

---

💖 DESCRIPTION 💖

So what she does is: she extracts the firmware node of the remote device that fwnode is pointing to. That's it. That's the function. Iconic, unbothered, does exactly one thing. 💅

⚠️ Okay this part is important and I need you to actually listen: the caller is responsible for calling fwnode_handle_put on the returned fwnode pointer. Like, you have to clean up after yourself. She hands you the pointer, you give it back. No leaking, no cap. 😭🧹

---

🌈 SEE ALSO 🌈

Sis brought her whole friend group, and honestly? The guest list is long but every single one of them is a real one. 💀 The kernel file is ./drivers/base/property.c, and here's everybody who showed up to the party:

• device_property_present(9)
• fwnode_property_present(9)
• device_property_read_bool(9)
• fwnode_property_read_bool(9)
• device_property_read_u8_array(9)
• device_property_read_u16_array(9)
• device_property_read_u32_array(9)
• device_property_read_u64_array(9)
• device_property_read_string_array(9)
• device_property_read_string(9)
• device_property_match_string(9)
• fwnode_property_read_u8_array(9)
• fwnode_property_read_u16_array(9)
• fwnode_property_read_u32_array(9)
• fwnode_property_read_u64_array(9)
• fwnode_property_read_string_array(9)
• fwnode_property_read_string(9)
• fwnode_property_match_string(9)
• fwnode_property_match_property_string(9)
• fwnode_property_get_reference_args(9)
• fwnode_find_reference(9)
• fwnode_get_name(9)
• fwnode_get_name_prefix(9)
• fwnode_name_eq(9)
• fwnode_get_parent(9)
• fwnode_get_next_parent(9)
• fwnode_count_parents(9)
• fwnode_get_nth_parent(9)
• fwnode_get_next_child_node(9)
• fwnode_get_next_available_child_node(9)
• device_get_next_child_node(9)
• fwnode_get_named_child_node(9)
• device_get_named_child_node(9)
• fwnode_handle_get(9)
• fwnode_device_is_available(9)
• fwnode_get_child_node_count(9)
• fwnode_get_named_child_node_count(9)
• fwnode_get_phy_mode(9)
• device_get_phy_mode(9)
• fwnode_iomap(9)
• fwnode_irq_get(9)
• fwnode_irq_get_byname(9)
• fwnode_graph_get_next_endpoint(9)
• fwnode_graph_get_port_parent(9)
• fwnode_graph_get_remote_port(9)
• fwnode_graph_get_remote_endpoint(9)
• fwnode_graph_get_endpoint_by_id(9)
• fwnode_graph_get_endpoint_count(9)
• fwnode_graph_parse_endpoint(9)
• fwnode_connection_find_match(9)
• fwnode_connection_find_matches(9)

---

And that's the whole page, bestie! 🧚‍♀️💜 This lil gem comes to you from the ./drivers/base directory, dated October 2026, and she's filed under fwnode_grap..._port_parent(9) because apparently even the title got cut off mid-sentence — relatable honestly 💀. Go forth, get your remote port parent, and put the fwnode when you're done. Periodt. 🎀🦋⭐