device_prope...ad_u32_array(9)

💅 device_prope...ad_u32_array(9) — like, the device_property_read_u32_array page, bestie

okay so this is a page from the Kernel API Manual, section 9 — yes, the big-kid kernel developer section 🧚✨ pull up a chair, we're reading firmware properties together.

---

✨ NAME ✨

device_property_read_u32_array — grab a whole u32 array property off a device and hand it back to you, no cap 💖

---

🌸 SYNOPSIS 🌸

int device_property_read_u32_array (const struct device *dev , const
       char *propname , u32 *val , size_t nval );

literally that's it. one function call and the array is yours, iykyk 🫶

---

🎀 ARGUMENTS 🎀

• dev — the device you're pulling the property off of. like, whose firmware description are we snooping through, bestie 👀
• propname — the name of the property. this is the string you're looking for 🔍
• val — this is where the values get stashed. or pass NULL here and instead it just tells you how many values there are — iconic dual-purpose behavior, periodt ✨
• nval — the size of the val array. just how much room you're giving it 🍓

---

💜 DESCRIPTION 💜

so the function reads an array of u32 properties with propname out of the device firmware description, and if it finds them it stores them into val. slay 🌈

ok important side note: it's recommended to call device_property_count_u32 instead of calling this function with val equals NULL and nval equals 0. like, that's the vibe-approved way to count, fr fr 🙈

---

🔥 RETURN 🔥

here's the vibe check on what you get back:

• number of values — if val was NULL 💫
• 0 — if the property was found (that's success, we ate) 👑
• -EINVAL — if the arguments you gave are not valid 😭
• -ENODATA — if the property doesn't have a value 💀
• -EPROTO — if the property is not an array of numbers 🌸
• -EOVERFLOW — if the size of the property is not as expected 🦋
• -ENXIO — if there's no suitable firmware interface present 😔

---

🌟 SEE ALSO 🌟

kernel file ./drivers/base/property.c, plus literally the entire 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_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_match(9)
• fwnode_connection_find_matches(9)

like, that's the whole group chat, go say hi 💅

---

ok bye bestie, go read some firmware properties 🫶 this page came from ./drivers/base and it's dated October 2026, and the header said device_prope...ad_u32_array(9) in case you forgot already 💖✨