rproc_get_by_child(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… rproc_get_by_child β€” from the Kernel API Manual, bestie ✨

Okay so picture this: it's a kernel API manual page, the title is rproc_get_by_child(9), and it's here to teach you how to acquire the rproc handle of @dev's ancestor 🫢. That's the whole vibe. Ancestor-hunting. Remote processor edition. Let's go πŸŽ€


✨ NAME ✨

rproc_get_by_child β€” literally goes and grabs you the rproc handle of @dev's ancestor πŸ‘‘

🌸 SYNOPSIS 🌸

struct rproc * rproc_get_by_child (struct device *dev );

That's it. One function, one argument, one struct rproc * coming back at you 😌

πŸ’– ARGUMENTS πŸ’–

  • dev β€” the child device whose ancestor we're trying to find 🧚 no cap, you hand it the kid and it goes looking up the family tree.

⭐ RETURN ⭐

It returns the ancestor rproc instance πŸŽ‰ β€” or NULL if it's not found πŸ’€ (so like, check for NULL, bestie, fr fr).

Not found = NULL. Don't be out here dereferencing a NULL and acting surprised πŸ™ˆ

πŸ”₯ SEE ALSO πŸ”₯

Bestie there are so many friends in this section, I'm obsessed 😭 The kernel file is ./drivers/remoteproc/remoteproc_core.c, and everything below lives in the same family:

Like I said. So many. A whole friend group πŸ«‚πŸ’œ


That's the page, bestie!! πŸ’…βœ¨ Shoutout to ./drivers/remoteproc (that's the source, mwah 😘) and the date on this iconic little artifact: October 2026 πŸ—“οΈπŸŒΈ Go forth and find those ancestors πŸ‘‘πŸ’–

πŸ“¦ where this page comes from