dmaengine_p...eral_dma_vec(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay so bestie, this page is from the Kernel API Manual and it's all about dmaengine_prep_peripheral_dma_vec β€” the function that prepares a DMA scatter-gather descriptor πŸŽ€

🌸 SYNOPSIS 🌸

struct dma_async_tx_descriptor * dmaengine_prep_peripheral_dma_vec
(struct dma_chan *chan , const struct dma_vec *vecs , size_t nents ,
enum dma_transfer_direction dir , unsigned long flags );

πŸ’… ARGUMENTS πŸ’…

  • chan β€” the channel to be used for this descriptor. it's giving "which lane are we driving in" energy πŸš—
  • vecs β€” the array of DMA vectors that should be transferred. literally the whole squad of vectors πŸ¦‹
  • nents β€” the number of DMA vectors in the array. yes, you gotta count them, no vibes-only guesses 😭
  • dir β€” specifies the direction of the data transfer. which way is the data going? main character question fr fr πŸ‘‘
  • flags β€” DMA engine flags. DMA_PREP_REPEAT can be used to mark a cyclic DMA transfer πŸ”
ngl bestie, that DMA_PREP_REPEAT flag is the one to remember β€” it's how you say "this transfer goes round and round" πŸ’«

🫢 SEE ALSO 🫢

Kernel file ./include/linux/dmaengine.h β€” and the whole extended fam, no cap:

that's the whole group chat, hope you said hi to everyone πŸ’œ


🧚 cute lil sign-off: this icon lives in ./include/linux, dated October 2026, and it's page dmaengine_p...eral_dma_vec(9) of the Kernel API Manual. slay, you're done, go prep some descriptors βœ¨πŸ’…
πŸ“¦ where this page comes from