zynqmp_dma_...erminate_all(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… zynqmp_dma_device_terminate_all(9) β€” bestie's guide to nuking every transfer on a channel ✨

okay so real talk, we're in the Kernel API Manual today and this page is genuinely iconic in the most "chaotic cleanup" way possible. Sit down, grab a strawberry drink πŸ“, and let's get into it.


🌸 NAME 🌸

zynqmp_dma_device_terminate_all β€” bestie, this one aborts all transfers on a channel. like, ALL of them. no survivors. it's giving "closing the group chat mid-argument." πŸ’€


πŸ¦‹ SYNOPSIS πŸ¦‹

int zynqmp_dma_device_terminate_all (struct dma_chan *dchan );

that's the whole vibe. one function, one pointer, one very confused DMA channel wondering what it did wrong. πŸ™ˆ


πŸŽ€ ARGUMENTS πŸŽ€

  • dchan β€” the DMA channel pointer πŸ’– this is the little main character we're about to shut down. hand it over and she does the rest. no cap.

⭐ RETURN ⭐

Always '0'. yep. always. it never fails, it never misses, it never gives you an error to debug at 3am. she's consistent like that. periodt. πŸ‘‘


πŸ”₯ SEE ALSO πŸ”₯

ok so there's a whole lore here and i'm obsessed. the kernel file lives at ./drivers/dma/xilinx/zynqmp_dma.c, and these are the structs and functions in the same little friend group:

  • struct zynqmp_dma_desc_ll(9)
  • struct zynqmp_dma_desc_sw(9)
  • struct zynqmp_dma_chan(9)
  • struct zynqmp_dma_device(9)

and now the full cast of characters, in order, no skipping, iykyk 🫢:

like, that's a whole friend group and terminate_all is the one who says "okay everyone go home." πŸ’€βœ¨


heads up bestie: this page doesn't list any options, env vars, exit statuses or error codes beyond that '0' β€” so there's literally nothing else to catch. we ate and left no crumbs. 🍽️

and that's the whole page, mwah πŸ’œ β€” straight out of ./drivers/dma/xilinx, dated October 2026. go forth and terminate responsibly, bestie πŸ§šβ€β™€οΈπŸŒˆ

πŸ“¦ where this page comes from