iio_push_to_buffers_with_ts(9)

💖 iio_push_to_buffers_with_ts(9) — like, the Kernel API Manual page, bestie ✨

okay so this is a page from the Kernel API Manual, and honestly? she's lowkey iconic. it's iio_push_to_buffers_with_ts(9), and she's about to make your sample data and your timestamp go to the right place. no cap. 🎀

---

✨ NAME ✨

iio_push_to_buffers_with_ts — push data and timestamp to buffers. that's the whole gig. data goes in, timestamp comes along for the ride. slay. 💅

---

🦋 SYNOPSIS 🦋

int iio_push_to_buffers_with_ts (struct iio_dev *indio_dev , void *data
, size_t data_total_len , s64 timestamp );

like, four things go in and an int comes out. it's giving function signature realness. 🔥

---

🌸 ARGUMENTS 🌸

the args!!! let me introduce you bestie, they're all main characters:

• indio_dev — the iio_dev structure for the device. your device's ✨identity✨ basically. the iio_dev struct girlies know.
• data — a pointer to the sample data buffer. it's the actual goods, the payload, the moment. 🙈
• data_total_len — the size of data, in bytes. yes, bytes. we measure in bytes here. ngl she's important because the buffer has to be big enough (more on that in a sec 👀).
• timestamp — the timestamp for the sample data, as an s64. she's a signed 64-bit icon and she is arriving. ⭐

---

💜 DESCRIPTION 💜

okay so here's the tea: this function pushes data to the IIO device's buffers. simple enough, right? but there's a plot twist 🫶

if timestamps are enabled for the device, the function will store the supplied timestamp as the last element in the sample data buffer before pushing it to the device buffers. so she's not just tagging along — she's literally getting tucked in at the end of your sample data. periodt. 💅

and because of that little maneuver, the sample data buffer needs to be large enough to hold the additional timestamp. usually the buffer should be at least indio->scan_bytes bytes large. 🌈

⚠️ bestie, do NOT forget that extra room for the timestamp. the buffer has to be big enough or it's giving undefined chaos. the man page says "needs to be large enough" and she means it fr fr. 😭

---

🧚 CONTEXT 🧚

Any context. that's it. that's the context section. she's versatile, she's flexible, she has no situational requirements. every context is her context. 👑

---

🔥 RETURN 🔥

• 0 on success — we love a clean zero 💖
• a negative error code otherwise — 😭😭😭 but at least it's a real errno situation and not a mystery

---

🎀 SEE ALSO 🎀

go read these next, bestie, they're literally the friends of this function:

• Kernel file ./include/linux/iio/buffer.h 👀
• iio_push_to_buffers_with_timestamp(9) — yes, the other one. you will be seeing her. ⭐

---

okay that's the whole page, and honestly she ate 💅💖

this little beauty lives in ./include/linux/iio, dated October 2026, and it's the iio_push_to_buffers_with_ts(9) page from the Kernel API Manual. mwah, love u, go push those buffers bestie 🫶💜🍓