rproc_del(9)

📦 version 7.3.1, in nixpkgs unstable

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

okay so you found the page for rproc_del(9), the little "actually, never mind" button for a remote processor. Sit down, hydrate, let's get into it 🫶

✨ NAME ✨

rproc_del — unregister a remote processor 🌸

✨ SYNOPSIS ✨

int rproc_del (struct rproc *rproc );

✨ ARGUMENTS ✨

  • rproc — the rproc handle you wanna unregister. like, the actual handle. not a vibe, an actual handle 💅

✨ DESCRIPTION ✨

So this is the function you call when your platform-specific rproc implementation has decided it's time to remove the rproc device. Girl, this is the breakup scene 😭

the one rule bestie: it should _only_ be called if a previous invocation of rproc_add has completed successfully. no successful rproc_add? no rproc_del. that's the whole vibe check. ⭐

And here's the plot twist — after rproc_del returns, rproc isn't freed yet. Not even a little. Why? because of the outstanding reference created by rproc_alloc. So to decrement that one last refcount, you still need to call rproc_free. It's giving "part one of a two-part finale" 🎀

✨ RETURN ✨

  • 0 on success 🎉
  • -EINVAL if rproc isn't valid 💀

✨ SEE ALSO ✨

Kernel file ./drivers/remoteproc/remoteproc_core.c, plus the whole friend group:

that's the whole page, no cap ✨ this one lives under ./drivers/remoteproc and it's dated October 2026 — so like, mark your calendar bestie, mwah 💖 🦋 🎀

📦 where this page comes from