pruss_request_mem_region(9)

💖 pruss_request_mem_region 💖

okay so bestie, welcome to the Kernel API Manual entry for pruss_request_mem_region — yes it's a real function, yes it's a (9) section one, and yes we're gonna get through it together 🌸

✨ NAME ✨

pruss_request_mem_region — request a memory resource 🎀

---

✨ SYNOPSIS ✨

int pruss_request_mem_region (struct pruss *pruss , enum pruss_mem
mem_id , struct pruss_mem_region *region );

like, look at that signature. it's giving "i would like one memory please" 💅

---

✨ ARGUMENTS ✨

• pruss — the pruss instance 🦋 (the main character of this whole situation)
• mem_id — the memory resource id ⭐ (which memory, bestie, be specific)
• region — pointer to the memory region structure to be filled in 💖 (you hand it a box, it fills the box)

---

✨ DESCRIPTION ✨

so here's the vibe: this function lets a client driver request a memory resource. and if it goes through — success, slay — the client driver owns that particular memory region until it gets released using the pruss_release_mem_region API. no cap, that's the whole loop. you ask, you get it, you own it, then you give it back 😭 don't forget the giving back part please.

---

✨ RETURN ✨

• 0 if the requested memory region is available 🥳 — and in that case, a pointer to the memory region is returned via region 🎁
• an error otherwise 💀

fr fr check that return value. 0 means you're up, anything else means the region wasn't available and you should not be out here acting like you own it 🙈

---

✨ SEE ALSO ✨

• Kernel file ./drivers/soc/ti/pruss.c 📁
• struct pruss_private_data(9)
• pruss_get(9)
• pruss_put(9)
• pruss_release_mem_region(9)
• pruss_cfg_get_gpmux(9)
• pruss_cfg_set_gpmux(9)
• pruss_cfg_gpimode(9)
• pruss_cfg_miirt_enable(9)
• pruss_cfg_xfr_enable(9)

like, the whole friend group is here, iykyk 👑

---

and that's the page!! sourced from ./drivers/soc/ti, dated October 2026 — mwah, go request your memory region bestie, you got this 💜✨🎀