IIO_DECLARE_BUFFER_WITH_TS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… IIO_DECLARE_BUFFER_WITH_TS(9) β€” Kernel API Manual, bestie edition πŸ’…

πŸŽ€ NAME πŸŽ€

IIO_DECLARE_BUFFER_WITH_TS β€” Declare a buffer with timestamp. That's the whole vibe: it's the macro that declares a buffer and makes room for the timestamp too. πŸ’–

🌸 SYNOPSIS 🌸

IIO_DECLARE_BUFFER_WITH_TS (type , name , count );

✨ ARGUMENTS ✨

  • type β€” the element type of the buffer. This is what each buffer slot is made of, okurrr.
  • name β€” the identifier name of the buffer. That's the name you'll use to refer to it, bestie.
  • count β€” the number of elements in the buffer. How many type girlies are fitting in here.

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so IIO_DECLARE_BUFFER_WITH_TS declares a buffer that is safe to use with iio_push_to_buffers_with_ts. No cap. 🫢

And it's not just doing the bare minimum: in addition to allocating enough space for count elements of type, it also allocates space for a s64 timestamp at the end of the buffer and ensures proper alignment of the timestamp. The way that it handles both the elements and the timestamp alignment is honestly iconic. ✨

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file first: ./include/linux/iio/iio.h β€” then the whole cross-reference lineup, because we stay connected:


Okay that's the whole page, bestie. Filing this under source/version ./include/linux/iio, October 2026, IIO_DECLARE_BUFFER_WITH_TS(9) β€” mwah, and slay your kernel build. πŸ’‹πŸ’–

πŸ“¦ where this page comes from