device_prop...ead_u8_array(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to the device_prop...ead_u8_array(9) page in the Kernel API Manual β€” let’s get into it πŸ’…βœ¨

✨ NAME ✨

device_property_read_u8_array β€” return a u8 array property of a device πŸ’–

🫢 SYNOPSIS 🫢

       int device_property_read_u8_array (const struct device *dev , const char
       *propname , u8 *val , size_t nval );

πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” Device to get the property of
  • propname β€” Name of the property
  • val β€” The values are stored here or NULL to return the number of values
  • nval β€” Size of the val array

🌸 DESCRIPTION 🌸

okay so this function reads an array of u8 properties with propname from the device firmware description and stores them to val if found. literally that’s the whole vibe πŸ¦‹

bestie tip: it’s recommended to call device_property_count_u8 instead of calling this function with val equals NULL and nval equals 0. no cap, that’s the move πŸ’…

πŸ”₯ RETURN πŸ”₯

here’s the vibe check on what comes back:

  • 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, plus the full SEE ALSO bestie roll call β€” no skipping, periodt:


mwah πŸ’‹ this page’s source/version is ./drivers/base, dated October 2026, and it’s the device_prop...ead_u8_array(9) page β€” iconic, fr fr 🌈⭐

πŸ“¦ where this page comes from