fwnode_prope...match_string(9)

✨ fwnode_property_match_string ✨

okay bestie, welcome to the Kernel API Manual 💖 this one's called fwnode_property_match_string and honestly? it's a little baddie with one job and it does it well. let's get into it 🎀

---

🌸 NAME 🌸

fwnode_property_match_string — find a string in an array and return index 👑

like... you give it a string, it tells you where that string is chillin' in the array. that's the whole vibe. iykyk 💅

---

🦋 SYNOPSIS 🦋

int fwnode_property_match_string (const struct fwnode_handle *fwnode ,
const char *propname , const char *string );

literally three things in, one int out. simple. iconic. no notes. ✨

---

🎀 ARGUMENTS 🎀

• fwnode — the firmware node you're getting the property of. this is the node, the main character 🫶
• propname — the name of the property that's holding the array. yes, the array one. that one 💖
• string — the string you're looking for. the one you're hunting down. go find her 🔍

---

💜 DESCRIPTION 💜

so here's the tea ☕ — this function goes looking for a given string inside a string array, and if it finds it? it hands you back the index. that's it. that's the whole function. it finds and it returns. slay 💅

---

🌈 RETURN 🌈

okay so what comes back, and what does it mean:

• the index, starting from 0, if the property was found (success! 🎉)
• -EINVAL if the given arguments are not valid 🙈
• -ENODATA if the property does not have a value 😭
• -EPROTO if the property is not an array of strings 💀
• -ENXIO if no suitable firmware interface is present 🧚

ngl bestie, that last three are all "something's off with the input or the environment" energy — nothing you did, it's just the vibes being wrong ✨

---

⭐ SEE ALSO ⭐

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

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

---

okay that's the page!! 🦋 and before you go — this little gem lives in ./drivers/base 🏠 and it's dated October 2026 🗓️ so yeah, mark your calendar bestie. mwah, go read your properties 💖✨🎀