device_property_read_string(9)

🎀 NAME 🎀

device_property_read_string — return a string property of a device. periodt, that's the whole name vibe. 💖

Welcome to the Kernel API Manual page for device_property_read_string(9) — manual name folded in right here, bestie, no header-line copy-paste required. 🫶

✨ SYNOPSIS ✨

the signature, exactly as it appears:

int device_property_read_string (const struct device *dev , const char
*propname , const char **val );

💅 ARGUMENTS 💅

• dev — the Device you're getting the property of. main character device energy 🎀
• propname — the name of the property. iykyk ✨
• val — the value is stored here. that's where the string lands 💖

🦋 DESCRIPTION 🦋

okay so here's the tea: the way that this function reads the property propname from the device firmware description and stores the value into val if it's found is iconic. and yes, the value is checked to be a string — fr fr. string vibe check passed or it's not passing at all. 💅

lowkey important: the value is checked to be a string, so don't come at it with a non-string property and expect good vibes.

🌈 RETURN 🌈

What you get back, bestie:

• 0 — the property was found (success) 🎉
• -EINVAL — given arguments are not valid 🙈
• -ENODATA — the property does not have a value 💀
• -EPROTO or -EILSEQ — the property type is not a string 😭
• -ENXIO — no suitable firmware interface is present 🫠

🔥 SEE ALSO 🔥

Kernel file ./drivers/base/property.c — the file in question. Also go say hi to the whole friend group, ngl it's huge:

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

---

💖 xoxo, your kernel bestie — source/version: ./drivers/base, date: October 2026, page: device_property_read_string(9). periodt 🎀