iio_dmaengin...er_setup_ext(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

iio_dmaengine_buffer_setup_ext β€” literally the glow-up moment where you set up a DMA buffer for an IIO device ✨

(also hiiii, this is from the Kernel API Manual, welcome to the group chat πŸ’…)


🌸 SYNOPSIS 🌸

struct iio_buffer * iio_dmaengine_buffer_setup_ext (struct device *dev ,
struct iio_dev *indio_dev , const char *channel , enum
iio_buffer_direction dir );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” the DMA channel consumer device, aka the main character doing the consuming 🫢
  • indio_dev β€” the IIO device you're attaching this buffer to, bestie gets a whole buffer, obsessed 😭
  • channel β€” the DMA channel name, and like, typically it's "rx" (iykyk) πŸ’œ
  • dir β€” the direction of the buffer, either in or out, pick your vibe 🌈

πŸ”₯ DESCRIPTION πŸ”₯

Okay so here's the tea β˜• β€” this function allocates a brand-new IIO buffer using devm_iio_dmaengine_buffer_alloc and then attaches it to an IIO device with iio_device_attach_buffer. Two steps, both iconic, no cap πŸ’…

It also appends the INDIO_BUFFER_HARDWARE mode to the supported modes of the IIO device, because your device deserves to have options, periodt πŸ‘‘

Once you're done using the buffer, iio_dmaengine_buffer_teardown should be used to release it β€” like, actually do this, don't just ghost the buffer πŸ™ˆ

⭐ SEE ALSO ⭐


k bye bestie, this page came from ./drivers/iio/buffer, dated October 2026, and I have to return to iio_dmaengin...er_setup_ext(9) now β€” slay your DMA setup for me πŸ’–βœ¨πŸ§š

πŸ“¦ where this page comes from