fwnode_get_parent(9)

💅 fwnode_get_parent(9) ✨

okay so bestie, welcome to the Kernel API Manual — this one's a little baby page about the fwnode_get_parent(9) function 🎀 and honestly it's short but she's important, so let's get into it 🫶

---

✨ NAME ✨

fwnode_get_parent — return parent firwmare node 🌸

(yes that spelling is literally what the page says, i'm not touching it, i don't make the rules 💀)

---

🌈 SYNOPSIS 🌈

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

like... she returns a struct fwnode_handle * and she takes one const struct fwnode_handle * and that's the whole vibe ✨

---

🦋 ARGUMENTS 🦋

• fwnode — the firmware whose parent is being retrieved, i.e. the node you're asking "who's ur mom" about 👑 fwnode is the placeholder name here btw, that's just how manpages talk

---

💖 DESCRIPTION 💖

ok so this is the part where you have to actually be responsible 😭

The caller is responsible for calling fwnode_handle_put on the returned fwnode pointer. 🚨

like no cap, if you get a pointer back you own a reference and you gotta give it back with fwnode_handle_put, otherwise you're leaking and that's not icon energy 🙈

---

⭐ RETURN ⭐

you get the parent firmware node of the given node if possible 🌱 — or NULL if there was no parent available 💀 (device at the top of the tree, you're on your own bestie)

---

🌸 SEE ALSO 🌸

first up, the source of truth is literally the kernel file ./drivers/base/property.c and the whole squad lives in ./drivers/base 🧚

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

like that's the whole friend group, and yes they all have (9) after them, iykyk 💅

---

and that's the page bestie!! 🎀 literally so short but so real

signing off from ./drivers/base — October 2026 ⭐ this page was brought to you by the Kernel API Manual, mwah 💖🦋