knav_pool_desc_unmap(9)

✨ knav_pool_desc_unmap ✨

okay so bestie, this is a kernel function from the Kernel API Manual, and honestly? it's giving "cleanup crew" energy. Let me put you on: knav_pool_desc_unmap is literally the Unmap descriptor after DMA transfer moment. Like, the transfer's done, the vibe check is passed, now we gotta unmap that descriptor. periodt. 💅

🦋 SYNOPSIS 🦋

void * knav_pool_desc_unmap (void *ph , dma_addr_t dma , unsigned dma_sz );

🌸 ARGUMENTS 🌸

• ph — the pool handle, aka your main character pass to the pool. you know her, you love her 🫶
• dma — the DMA address of the descriptor you're tryna unmap. literally the address, no cap 📍
• dma_sz — the size of the descriptor to unmap. gotta know how big it is bestie, that's just facts 🔥

💖 RETURN 💖

on success it returns the descriptor address. slay! but ngl, don't just assume it's all good — use IS_ERR_OR_NULL to identify error values on return. like, please check before you trust it, i'm begging 😭✨

👑 SEE ALSO 👑

knav queue and pool lore, for when you're deep in the rabbit hole and honestly obsessed:

• Kernel file ./drivers/soc/ti/knav_qmss_queue.c
• knav_queue_notify(9)
• knav_queue_open(9)
• knav_queue_close(9)
• knav_queue_device_control(9)
• knav_queue_push(9)
• knav_queue_pop(9)
• knav_pool_create(9)
• knav_pool_destroy(9)
• knav_pool_desc_get(9)
• knav_pool_desc_put(9)
• knav_pool_desc_map(9)
• knav_pool_count(9)

bestie reminder: this one's from ./drivers/soc/ti, stamped October 2026, version 9 of the page. iconic era honestly 💜

mwah, go unmap those descriptors responsibly 🧚‍♀️