xilinx_dma_calc_copysize(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

xilinx_dma_calc_copysize β€” literally just calculates how much data needs to be copied πŸ’…

So okay, this is a page from the Kernel API Manual (yes that's the manual name, we're fancy here), and it's all about one little function that does one little job: math on copy sizes. Let's get into it bestie 🫢


🌸 SYNOPSIS 🌸

int xilinx_dma_calc_copysize (struct xilinx_dma_chan *chan , int size ,
int done );

That's the whole signature, no cap. Takes a channel, takes some sizes, gives you back an int. Iconic, honestly.


πŸŽ€ ARGUMENTS πŸŽ€

  • chan β€” the driver-specific DMA channel πŸ¦‹ like, the actual channel this is all happening on.
  • size β€” the total amount of data that needs to be copied. the whole snack. πŸ“
  • done β€” the amount of data that has already been copied. the part you already ate, bestie 😭

πŸ‘‘ RETURN πŸ‘‘

Returns the amount of data that has to be copied. That's it, that's the vibe check result. ✨


πŸ’œ SEE ALSO πŸ’œ

Sibling functions, structs, and enums β€” the whole group chat 🫢 and also the kernel file they all live in:


That's the whole page, bestie, go forth and copy exactly the right number of bytes πŸ’–βœ¨

source location: ./drivers/dma/xilinx Β· dated: October 2026 Β· xilinx_dma_calc_copysize(9) β€” mwah, see u in the kernel source πŸ§šπŸ’…

πŸ“¦ where this page comes from