device_prop...string_array(9)

📦 version 7.3.1, in nixpkgs unstable

💅 device_property_read_string_array — Kernel API Manual, bestie edition

okay so you're in the Kernel API Manual and you found device_property_read_string_array(9) — and honestly? she's giving "let me grab that string array off your device real quick." Let's get into it 🎀

✨ NAME ✨

device_property_read_string_array — return a string array property of device 🌸

🦋 SYNOPSIS 🦋

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

💖 ARGUMENTS 💖

  • dev — the device you wanna get the property of. her. the main character 👑
  • propname — name of the property, iykyk 🏷️
  • val — the values get stored here. or pass NULL if you just want the number of values 🫶
  • nval — size of the val array, so like, how much room you're giving her 💅

🌈 DESCRIPTION 🌈

So the function reads an array of string properties with propname from the device firmware description, and stores them into val if it finds them. literally that's it, slay ✨

it's recommended to call device_property_string_array_count instead of calling this function with val equals NULL and nval equals 0. no cap, that's the move 💯

🔥 RETURN 🔥

bestie here's the vibes breakdown of what you get back:

  • number of values read on success if val is non-NULL 💖
  • number of values available on success if val is NULL ⭐
  • -EINVAL if given arguments are not valid 🙈
  • -ENODATA if the property does not have a value 😭
  • -EPROTO or -EILSEQ if the property is not an array of strings 💀
  • -EOVERFLOW if the size of the property is not as expected 🫠
  • -ENXIO if no suitable firmware interface is present 🧚

🌸 SEE ALSO 🌸

the whole friend group fr fr — kernel file ./drivers/base/property.c plus:

and that's the whole page, periodt 💅 huge shoutout to ./drivers/base for holding it down — page dated October 2026, so she's fresh 🍓 bye bestie, go read some string arrays 🫶✨

📦 where this page comes from