device_prope...ad_u64_array(9)

✨ NAME ✨

okay bestie, welcome to the device_prope...ad_u64_array(9) page from the Kernel API Manual ✨ this is all about device_property_read_u64_array — it returns a u64 array property of a device, no cap 💅

---

🦋 SYNOPSIS 🦋

the signature, character for character, because we do not freestyle code:

int device_property_read_u64_array (const struct device *dev , const
       char *propname , u64 *val , size_t nval );

---

🎀 ARGUMENTS 🎀

• dev — the device you’re getting the property of, bestie 🫶
• propname — name of the property, yep that one
• val — the values are stored here, or NULL to return the number of values 👀
• nval — size of the val array

---

💅 DESCRIPTION 💅

so this function reads an array of u64 properties with propname from the device firmware description and stores them to val if found ✨ literally that’s the whole read.

it’s recommended to call device_property_count_u64 instead of calling this function with val equals NULL and nval equals 0 — like, save yourself the weird little caller era, bestie 🙈

---

🔥 RETURN 🔥

• the number of values if val was NULL
• 0 if the property was found (success) ✅
• -EINVAL if given arguments are not valid
• -ENODATA if the property does not 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 no suitable firmware interface is present

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/base/property.c — and here’s the whole friend group, every single one, no skips 💖

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

---

okay that’s the whole vibe 💖 source/version: ./drivers/base; date: October 2026; manual: Kernel API Manual; page: device_prope...ad_u64_array(9) 🫶✨