devm_dma_request_chan(9)

💅 devm_dma_request_chan(9) — the managed-channel glow-up

okay bestie, welcome to the Kernel API Manual page for devm_dma_request_chan(9) ✨ ngl this one is short but it's so useful — it's the "try to allocate an exclusive slave channel" girlie, and she comes with built-in cleanup energy 🎀

---

🌸 NAME 🌸

devm_dma_request_chan — try to allocate an exclusive slave channel 🦋

---

✨ SYNOPSIS ✨

struct dma_chan * devm_dma_request_chan (struct device *dev , const char
*name );

---

🫶 ARGUMENTS 🫶

• dev — pointer to client device structure 💖 (the device that's doing the asking, iykyk)
• name — slave channel name ⭐ (yes queen, tell it which channel you want)

---

👑 DESCRIPTION 👑

So like, this function returns a pointer to the appropriate DMA channel on success, or an error pointer 😭 — that's the whole vibe check. Either you get your channel or you get a sad little error pointer, no in-between 💀

The operation is managed, and it will be undone on driver detach 🧚 periodt. That's the devm_ part doing its main character work — no manual cleanup era, the kernel handles it for you when the driver dips 🙈

lowkey the best part: you don't have to remember to release it. The managed lifecycle ate and left no crumbs 💅

---

🔥 SEE ALSO 🔥

Kernel file ./drivers/dma/dmaengine.c 🍓 and all her friends:

• dev_to_dma_chan(9)
• struct dma_chan_tbl_ent(9)
• dma_chan_is_local(9)
• min_chan(9)
• dma_channel_rebalance(9)
• balance_ref_count(9)
• dma_chan_get(9)
• dma_chan_put(9)
• dma_find_channel(9)
• dma_issue_pending_all(9)
• dma_get_slave_channel(9)
• __dma_request_channel(9)
• dma_request_chan(9)
• dma_request_chan_by_mask(9)
• dmaengine_get(9)
• dmaengine_put(9)
• dma_async_device_register(9)
• dma_async_device_unregister(9)
• dmaenginem_async_device_register(9)
• dma_wait_for_async_tx(9)
• dma_run_dependencies(9)

---

and that's the whole page, bestie 💜 written from ./drivers/dma, dated October 2026, under the manual name devm_dma_request_chan(9) — slay, go request your channel, you've got this 🌈🎀