of_property_read_u32_array(9)

📦 version 7.3.1, in nixpkgs unstable

✨ of_property_read_u32_array(9) ✨

okay so bestie, welcome to the Kernel API Manual 🎀 — this is the page for of_property_read_u32_array, and it's literally the glow-up you need for reading a whole lil squad of 32-bit integers out of a device-tree property. no cap, it's iconic.

🌸 NAME 🌸

of_property_read_u32_array — find and read an array of 32 bit integers from a property 💅

🦋 SYNOPSIS 🦋

int of_property_read_u32_array (const struct device_node *np , const
       char *propname , u32 *out_values , size_t sz );

like, that's the whole vibe right there ⭐

💖 ARGUMENTS 💖

  • np — the device node you're reading the property value from. your main character node, basically 👑
  • propname — the name of the property to be searched. this is the thing you're hunting for, iykyk 🔍
  • out_values — pointer to the return value. heads up though: it only gets modified if the return value is 0. so no sneaky writes on failure, periodt 🙈
  • sz — the number of array elements to read. that's how many lil u32s you're asking for, fr fr

✨ DESCRIPTION ✨

Search for a property in a device node and read 32-bit value(s) from it. that's the whole assignment, bestie 💜

the way that out_values is modified only if a valid u32 value can be decoded — that's the safety vibe check, and we love her for it 🫶

🔥 RETURN 🔥

  • 0 on success — slay, you did it 🎉
  • -EINVAL if the property does not exist 😭
  • -ENODATA if property does not have a value 💀
  • -EOVERFLOW if the property data isn't large enough — like, not enough room, bestie, it's giving "buffer said no" 🍓

🌈 SEE ALSO 🌈

Kernel file ./include/linux/of.h — and the whole friend group:

bestie reminder: this page lives at ./include/linux, it's dated October 2026, and the whole thing is filed under of_property_read_u32_array(9). mwah 💋 go read some u32s, queen 🧚‍♀️
📦 where this page comes from