afu_dma_unpin_pages(9)

📦 version 7.3.1, in nixpkgs unstable

💅 afu_dma_unpin_pages — bestie edition

okay so this is a page straight out of the Kernel API Manual, and it's about afu_dma_unpin_pages, which is literally the "actually, you can let go now" moment for DMA memory. no cap, it's a short one, but she's important 💖

✨ NAME ✨

afu_dma_unpin_pages — unpin pages of given dma memory region 🦋

so yeah, she unpins pages. from a dma memory region. that's the whole vibe.

🌸 SYNOPSIS 🌸

void afu_dma_unpin_pages (struct dfl_feature_dev_data *fdata , struct
dfl_afu_dma_region *region );

notice the void? she gives nothing back, she just does the thing and leaves. main character energy tbh 👑

🎀 ARGUMENTS 🎀

  • fdata — feature dev data. that's it, that's the description. it's the feature dev data, bestie, she said what she said 💅
  • region — the dma memory region to be unpinned. this is the one getting un-pinned. say bye 🫶

🌈 DESCRIPTION 🌈

Unpin all the pages of the given dfl_afu_dma_region. every single one. not some, not most — all.

Return 0 for success or negative error code. ✨

⭐ heads up: the manpage literally says both "return 0 for success or negative error code" and declares the function void up in the synopsis. that's what the original says, so we're reporting it exactly, no editing, no notes 🙈

🔥 SEE ALSO 🔥

Kernel file ./drivers/fpga/dfl-afu-dma-region.c — go read the source, iykyk 🧚

like a whole little friend group of functions, and she's the one that cleans up 💜

sign-off time 🎀✨

this little gem lives in ./drivers/fpga, and it's dated October 2026 — future girlie behavior fr fr. that's the source and the date, both accounted for, nothing skipped, we ate and left no crumbs 💅🍓

k byeee, go unpin those pages bestie 💖🦋🌸

📦 where this page comes from