device_prope...ad_u16_array(9)

📦 version 7.3.1, in nixpkgs unstable

🌈 device_property_read_u16_array(9) — Kernel API Manual glow-up 🌈

okay so bestie, welcome to the Kernel API Manual page for device_property_read_u16_array(9). This is the one that returns a u16 array property of a device, and we're gonna read it together. no cap. 💖

✨ NAME ✨

device_property_read_u16_array — return a u16 array property of a device. periodt.

🎀 SYNOPSIS 🎀

int device_property_read_u16_array (const struct device *dev , const char *propname , u16 *val , size_t nval );

🦋 ARGUMENTS 🦋

  • dev — Device to get the property of. main character device energy.
  • propname — Name of the property. iykyk.
  • val — The values are stored here or NULL to return the number of values. cute.
  • nval — Size of the val array. don't forget this one.

🌸 DESCRIPTION 🌸

Function reads an array of u16 properties with propname from the device firmware description and stores them to val if found. slay. ✨

It's recommended to call device_property_count_u16 instead of calling this function with val equals NULL and nval equals 0. lowkey important, bestie.

🔥 RETURN 🔥

Here's the vibe check on what comes back: 👀

  • number of values if val was NULL — the count girlie.
  • 0 if the property was found (success) — we love a win.
  • -EINVAL if given arguments are not valid — check ur args, bestie.
  • -ENODATA if the property does not have a value — no data, no drama.
  • -EPROTO if the property is not an array of numbers — not the numeric array vibe.
  • -EOVERFLOW if the size of the property is not as expected — size said no.
  • -ENXIO if no suitable firmware interface is present. — no interface, no entry.

👑 SEE ALSO 👑

Kernel file: ./drivers/base/property.c

that's the whole page, bestie 🫶 source/version: ./drivers/base · October 2026 · device_prope...ad_u16_array(9) — mwah 💋

📦 where this page comes from