rproc_shutdown(9)

📦 version 7.3.1, in nixpkgs unstable

💖 NAME 💖

Okay so bestie, meet rproc_shutdown(9) from the Kernel API Manual 🫶. She is the “power off the remote processor” girlie, and yes, that is her whole iconic brand.

🛠️ SYNOPSIS 🛠️

int rproc_shutdown (struct rproc *rproc );

🎀 ARGUMENTS 🎀

  • rproc — the remote processor. That's the one and only argument, bestie.

🦋 DESCRIPTION 🦋

This function powers off a remote processor — specifically one that was previously booted with rproc_boot ✨.

But wait: if rproc is still being used by an additional user(s), then this function will just decrement the power refcount and exit, without really powering off the device. Lowkey important — it doesn't force a shutdown if somebody else is still holding on.

Every call to rproc_boot must (eventually) be accompanied by a call to rproc_shutdown. That's the matching-set situation, iykyk. Calling rproc_shutdown redundantly is a bug — not a cute little accident, an actual bug 💀.

🧚 NOTES 🧚

  • we're not decrementing the rproc's refcount, only the power refcount. which means that the rproc handle stays valid even after rproc_shutdown returns, and users can still use it with a subsequent rproc_boot, if needed. handle stays valid = iconic behavior 💅

🌈 RETURN 🌈

0 on success, and an appropriate error value otherwise. That's it: success gives you 0, and anything else is an appropriate error value. No mystery, no cap.

👑 SEE ALSO 👑

The kernel file ./drivers/remoteproc/remoteproc_core.c is in the group chat, plus all these besties:

Signed with love from the source/version stamp ./drivers/remoteproc, dated October 2026, and this page is rproc_shutdown(9). Bye bestie — go pair your boots and shutdowns responsibly 💜🎀

📦 where this page comes from