build_channel_array(9)

✨ build_channel_array — like, the manual page 💅

okay so this is a page from the Kernel API Manual, bestie — section 9, kernel API vibes only. sit down, grab a strawberry 🍓, and let's get into it.

---

🌸 NAME 🌸

build_channel_array — literally the function that figures out what channels are present 👑

---

🦋 SYNOPSIS 🦋

int build_channel_array (const char *device_dir , int buffer_idx ,
       struct iio_channel_info **ci_array , int *counter );

---

🎀 ARGUMENTS 🎀

• device_dir — the IIO device directory in sysfs. that's the spot she lives in, periodt 💖
• buffer_idx — the IIO buffer for this channel array. yes, specifically this one ✨
• ci_array — output: the resulting array of iio_channel_info. she fills this in for you 🫶
• counter — output: the amount of array elements. so you know how many you got, no cap 🔢

---

💜 DESCRIPTION 💜

Returns 0 on success — iconic, flawless, ate 💅. Otherwise it hands back a negative error code, which is the vibe check failing, and you should probably go look at that 😭.

---

🌈 SEE ALSO 🌈

Kernel file ./tools/iio/iio_utils.c — that's where the magic lives, iykyk 👀

and also, all of these besties:

• iioutils_break_up_name(9)
• iioutils_get_type(9)
• iioutils_get_param_float(9)
• bsort_channel_array_by_index(9)
• find_type_by_name(9)
• write_sysfs_int(9)
• write_sysfs_int_and_verify(9)
• write_sysfs_string_and_verify(9)
• write_sysfs_string(9)
• read_sysfs_posint(9)
• read_sysfs_float(9)
• read_sysfs_string(9)

---

fr fr, that's the whole page. no filler, no skips, every single reference accounted for 🧚

okay bye ily, this page came from ./tools/iio and it's dated October 2026 — mwah, see u in the next one 💖✨🎀