fwnode_graph..._port_parent(9)

💅 fwnode_graph_get_port_parent — the Kernel API Manual, bestie edition ✨

Okay so you're in the <pink>Kernel API Manual</pink>, land of the <purple>fwnode_graph..._port_parent(9)</purple> page, and honestly? This one is short and sweet. Let's get into it 🎀

---

🌸 NAME 🌸

fwnode_graph_get_port_parent — this one hands you back the device fwnode of a port endpoint. That's the vibe 💫

---

✨ SYNOPSIS ✨

struct fwnode_handle * fwnode_graph_get_port_parent (const struct fwnode_handle *endpoint );

Like, literally that. Signature stays exactly like that, no cap 🫶

---

🦋 ARGUMENTS 🦋

• endpoint — the endpoint firmware node of the port. That's the thing you're passing in, bestie 💖

---

🧚 DESCRIPTION 🧚

So the one thing you cannot forget here: the caller is responsible for calling fwnode_handle_put on the returned fwnode pointer. That's on you, main character. Nobody's gonna clean that up for you 😭 Own your refcounts, periodt.

---

👑 RETURN 👑

It gives you back the firmware node of the device the endpoint belongs to. Iconic. That's the whole return value 🌈 (and remember the fwnode_handle_put thing from up there, fr fr)

---

⭐ SEE ALSO ⭐

Kernel file: ./drivers/base/property.c

And now the whole crew, because they all come as a package deal 💅

• 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_remote_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)

---

Quick vibe check: every single one of those (9) references is legit, don't skip 'em — that's your reading list for the day 📚✨

---

And that's the page, bestie! 🫶 This little beauty lives in ./drivers/base, dated October 2026, filed under fwnode_graph..._port_parent(9). Go forth, grab your port parent, and please remember the fwnode_handle_put. Mwah 💋