rproc_add_subdev(9)

📦 version 7.3.1, in nixpkgs unstable

💅 NAME 💅

rproc_add_subdev — bestie, this is the one that adds a subdevice to a remoteproc ✨

So like, we're in the Kernel API Manual, page rproc_add_subdev(9), and honestly? It's giving "small function, big responsibilities." Let's get into it 🫶

🌸 SYNOPSIS 🌸

void rproc_add_subdev (struct rproc *rproc , struct rproc_subdev *subdev
);

Yeah that's it. Two args, no return value, void and unbothered 💀

🎀 ARGUMENTS 🎀

  • rproc — the rproc handle you're adding the subdevice to 👑 like, this is the main character's home, okay?
  • subdev — the subdev handle you're registering 🌸 this is the little guy moving in.

🦋 DESCRIPTION 🦋

Okay so real talk: the caller is responsible for populating the optional subdevice function pointers. That's on you, bestie. Not the function's problem. Not the kernel's problem. Yours 🙈

So like, before you call this, make sure you've filled in whatever optional function pointers your subdevice needs. rproc_add_subdev is not gonna do it for you — no cap, it literally just adds and registers. The rest? That's your lore to write ✍️

⭐ SEE ALSO ⭐

Lowkey the longest SEE ALSO ever, but we don't gatekeep here 💖 First up, the kernel file it lives in:

./drivers/remoteproc/remoteproc_core.c

And then, the whole friend group:

Go read them all, iykyk 📚✨ (also rproc_remove_subdev is right there at the end — foreshadowing, bestie 💀)

Reminder boo: populate those optional function pointers before you call this. That's the whole caveat and it's non-negotiable 🎀

Okay that's the whole page! This one's from the ./drivers/remoteproc corner of the kernel, dated October 2026, and it's rproc_add_subdev(9) — slay, go add some subdevices responsibly 💜🌈⭐

📦 where this page comes from