xilinx_dma_calc_copysize(9)
β¨ 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:
- Kernel file
./drivers/dma/xilinx/xilinx_dma.c struct xilinx_vdma_desc_hw(9)struct xilinx_axidma_desc_hw(9)struct xilinx_aximcdma_desc_hw(9)struct xilinx_cdma_desc_hw(9)struct xilinx_vdma_tx_segment(9)struct xilinx_axidma_tx_segment(9)struct xilinx_aximcdma_tx_segment(9)struct xilinx_cdma_tx_segment(9)struct xilinx_dma_tx_descriptor(9)struct xilinx_dma_chan(9)enum xdma_ip_type(9)struct xilinx_dma_device(9)vdma_desc_write_64(9)xilinx_dma_get_metadata_ptr(9)xilinx_vdma_alloc_tx_segment(9)xilinx_cdma_alloc_tx_segment(9)xilinx_axidma_alloc_tx_segment(9)xilinx_aximcdma_alloc_tx_segment(9)xilinx_dma_free_tx_segment(9)xilinx_mcdma_free_tx_segment(9)xilinx_cdma_free_tx_segment(9)xilinx_vdma_free_tx_segment(9)xilinx_dma_alloc_tx_descriptor(9)xilinx_dma_free_tx_descriptor(9)xilinx_dma_free_desc_list(9)xilinx_dma_free_descriptors(9)xilinx_dma_free_chan_resources(9)xilinx_dma_get_residue(9)xilinx_dma_chan_handle_cyclic(9)xilinx_dma_chan_desc_cleanup(9)xilinx_dma_do_tasklet(9)xilinx_dma_alloc_chan_resources(9)xilinx_dma_tx_status(9)xilinx_dma_stop_transfer(9)xilinx_cdma_stop_transfer(9)xilinx_dma_start(9)xilinx_vdma_start_transfer(9)xilinx_cdma_start_transfer(9)xilinx_dma_start_transfer(9)xilinx_mcdma_start_transfer(9)xilinx_dma_issue_pending(9)xilinx_dma_device_config(9)xilinx_dma_complete_descriptor(9)xilinx_dma_reset(9)xilinx_dma_chan_reset(9)xilinx_mcdma_irq_handler(9)xilinx_dma_irq_handler(9)append_desc_queue(9)xilinx_dma_tx_submit(9)xilinx_vdma_dma_prep_interleaved(9)xilinx_cdma_prep_memcpy(9)xilinx_dma_prep_peripheral_dma_vec(9)xilinx_dma_prep_slave_sg(9)xilinx_dma_prep_dma_cyclic(9)xilinx_mcdma_prep_slave_sg(9)xilinx_dma_terminate_all(9)xilinx_vdma_channel_set_config(9)xilinx_dma_chan_remove(9)xilinx_dma_chan_probe(9)xilinx_dma_child_probe(9)of_dma_xilinx_xlate(9)xilinx_dma_probe(9)xilinx_dma_remove(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms