dmaengine_de...lback_invoke(9)

💅 dmaengine_desc_get_callback_invoke — Kernel API Manual ✨

okay so bestie, we're in the Kernel API Manual today and this one is genuinely a little shortcut function. no cap. 🎀

---

🌸 NAME 🌸

dmaengine_desc_get_callback_invoke — get the callback in tx descriptor and then immediately call the callback. like, it literally does both things back to back, no pause, no nothing 💖

---

✨ SYNOPSIS ✨

void dmaengine_desc_get_callback_invoke (struct dma_async_tx_descriptor
*tx , const struct dmaengine_result *result );

---

🦋 ARGUMENTS 🦋

• tx — dma async tx descriptor. this is the descriptor we're pulling the callback out of, periodt 🫶
• result — transaction result. the outcome, the receipt, the vibe check of how the transaction went 💀

---

🌈 DESCRIPTION 🌈

so here's the tea: this function calls dmaengine_desc_get_callback and dmaengine_desc_callback_invoke in a single function, because there is literally no work necessary in between for the driver. like none. zero. so why make the driver do it in two steps? exactly. iconic behavior honestly 👑

Locking is dependent on the driver. — yes bestie, that means you, the driver, you're in charge of the locking situation. we don't handle that for you 🙈

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/dma/dmaengine.h
• dma_cookie_init(9)
• dma_cookie_assign(9)
• dma_cookie_complete(9)
• dma_cookie_status(9)
• dmaengine_desc_get_callback(9)
• dmaengine_desc_callback_invoke(9)
• dmaengine_desc_callback_valid(9)

---

and that's the whole page bestie, from the kernel file ./drivers/dma, dated October 2026 💜 go forth and invoke your callbacks responsibly 🧚‍♀️⭐