pruss_get(9)

💖 pruss_get(9) 💖

okay so this is a page from the Kernel API Manual and honestly? it's a little baddie. it's pruss_get, and it's giving "i just want my PRU to find its parent." let's get into it 🎀

---

✨ NAME ✨

pruss_get — get the pruss for a given PRU remoteproc 💅

---

🌸 SYNOPSIS 🌸

struct pruss * pruss_get (struct rproc *rproc );

like. that's the whole vibe. one function, one job.

---

🦋 ARGUMENTS 🦋

• rproc — the remoteproc handle of a PRU instance. that's your girl. that's who you're asking about 🫶

---

💜 DESCRIPTION 💜

okay bestie, so what this does: it finds the parent pruss device for a PRU, given the rproc handle of that PRU remote processor. matchmaker energy fr fr 🌈

and here's the part you cannot skip: this function increments the pruss device's refcount. so you always gotta use pruss_put to decrement it back once you don't need the pruss anymore. no leaving it hanging, that's rude 😭

⚠️ also important: this API doesn't check if rproc is valid or not. nope. not its job. it fully expects the caller to have done a pru_rproc_get on rproc before calling this API, so that rproc is guaranteed valid. do your homework first, bestie 💀

---

⭐ RETURN ⭐

• success — you get a pruss handle. slay 👑
• failure — you get an ERR_PTR, using one of these error values:
  • -EINVAL — invalid parameter 🙈
  • -ENODEV — the PRU device or the PRUSS device is not found 💀

---

🧚 SEE ALSO 🧚

• Kernel file ./drivers/soc/ti/pruss.c
• struct pruss_private_data(9)
• pruss_put(9)
• pruss_request_mem_region(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 a whole friend group of pruss functions. iykyk 💖

---

okay that's the page!! and for the little sign-off moment: this one lives under ./drivers/soc/ti, dated October 2026, and it's filed as pruss_get(9) — iconic, periodt 🍓✨💅