qcom_remove_ssr_subdev(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… qcom_remove_ssr_subdev β€” bestie's guide to un-subdevving your SSR notifier

okay so real talk, this one lives in the Kernel API Manual, section 9, and it's literally called qcom_remove_ssr_subdev(9). yes that's a mouthful, no i will not be shortening it, it's iconic πŸ’–


🌸 NAME 🌸

qcom_remove_ssr_subdev β€” the function that removes a subdevice as a restart notification source. that's it. that's the whole vibe. it's the cleanup era, the "we're so done here" moment, the goodbye text after the group chat goes quiet πŸ¦‹


✨ SYNOPSIS ✨

void qcom_remove_ssr_subdev (struct rproc *rproc , struct qcom_rproc_ssr *ssr );

returns void, meaning it gives you nothing back β€” no return value, no "did it work", just vibes and the sweet release of deregistration. slay.


πŸŽ€ ARGUMENTS πŸŽ€

  • rproc β€” the rproc handle. you know, the remoteproc. your main character. pass it in, be normal about it 🫢
  • ssr β€” the SSR subdevice handle. this is the one getting removed from the notification-source roster. pour one out 😭
ngl bestie, both of these are pointers and both of them need to actually be your pointers. no cap.

πŸ‘‘ SEE ALSO πŸ‘‘

if you're the type to fall down a rabbit hole (and honestly? same), here's the whole friend group β€” all of these are chillin' in the kernel file ./drivers/remoteproc/qcom_common.c:

like, the way this page's SEE ALSO section is basically a whole linked list of friends? we love a supportive ecosystem. periodt. πŸ’œ


heads up: this page is brought to you by the folk(s) hanging out in ./drivers/remoteproc, dated October 2026. that's the source, that's the version stamp, that's the little footer energy β€” mwah, bye, go remove your subdev responsibly πŸ§šβ€β™€οΈβ­
πŸ“¦ where this page comes from