devm_cpm_muram_alloc(9)

💅 devm_cpm_muram_alloc(9) — from the Kernel API Manual, bestie 🎀

okay so picture this: you're poking around in kernel-land and you need some muram. this is the page for that. periodt. ✨

---

✨ NAME ✨

devm_cpm_muram_alloc — literally the resource-managed version of cpm_muram_alloc, and yes that's the whole vibe 🫶

---

🌸 SYNOPSIS 🌸

s32 devm_cpm_muram_alloc (struct device *dev , unsigned long size ,
       unsigned long align );

look at her. three params, one s32 return, zero notes. iconic. 👑

---

🦋 ARGUMENTS 🦋

• dev — the Device you're allocating memory for 🫶 (yes, the struct itself, not a copy, not a vibe)
• size — number of bytes to allocate. the amount. the quantity. the size, bestie 💖
• align — the requested alignment, in bytes. alignment matters, ngl 🎯

---

💜 DESCRIPTION 💜

So this function hands you back a non-negative offset into the muram area, or a negative errno on failure — exactly like cpm_muram_alloc does. fr fr. 😭 That's the deal.

When you've got your offset and you want the actual virtual address of that area? That's when you call cpm_muram_addr. she's the one who knows where things live 💅

Now here's the part where this one is different, and it's giving main character energy: compare it against plain cpm_muram_alloc, because the memory allocated by this resource-managed version is automatically freed on driver detach. 🧚✨

🚨 which means — say it with me — cpm_muram_free must NOT be called to release the allocated memory. not ever. do not do it. the devm machinery has it handled, and if you double-free it that's on you bestie 💀

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/soc/fsl/qe/qe_common.c 📁
• cpm_muram_free(9)
• devm_cpm_muram_alloc_fixed(9)
• cpm_muram_addr(9)
• cpm_muram_dma(9)

---

and that's the whole page, no cap 🍓 this gem lives over in ./drivers/soc/fsl/qe and got stamped October 2026 — so like, go forth and allocate responsibly, and remember: devm frees it for you, you just look pretty 💖💅🌟