fwnode_conne...n_find_match(9)

💅 fwnode_connection_find_match(9) — like, the Kernel API Manual, bestie 🎀

okay so you found the page for fwnode_connection_find_match in the kernel API manual and honestly? good for you. let's get into it 💖

---

✨ NAME ✨

fwnode_connection_find_match — find a connection from a device node 🦋

---

🌸 SYNOPSIS 🌸

void * fwnode_connection_find_match (const struct fwnode_handle *fwnode
, const char *con_id , void *data , devcon_match_fn_t match );

literally the whole signature, no notes 👑

---

🎀 ARGUMENTS 🎀

• fwnode — the device node that's got the connection, like it's holding it for you 🫶
• con_id — the identifier for the connection. its little name tag basically 💅
• data — the data you're handing over to the match function ✨
• match — the function that checks the connection description and converts it. the one doing the actual work ngl 💀

---

🔥 DESCRIPTION 🔥

So here's the vibe: you've got fwnode, you've got some other device node, and this function goes and finds the connection between them that has the unique identifier con_id. cute, right?

And then match? match is the main character here 🎀 it takes that connection description and converts it into the data that you, the caller, are expecting to get back. so like, it's giving translator. it's giving glow-up for a raw description. obsessed 💖

---

👑 SEE ALSO 👑

Kernel file ./drivers/base/property.c, plus the whole friend group:

• 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_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_matches(9)

---

that's the whole page, no cap 🌈 and yeah — this one lives in ./drivers/base, dated October 2026, and it's from the kernel API manual itself. mwah, go read some kernel source bestie 💜🧚‍♀️