qcom_add_ssr_subdev(9)

🎀 qcom_add_ssr_subdev — kernel API manual, bestie edition 🎀

okay so real talk, this is a page from the Kernel API Manual and it's about qcom_add_ssr_subdev(9). yes the name is a mouthful, no we're not renaming it. let's go 💅

---

✨ NAME ✨

qcom_add_ssr_subdev — literally just registers a subdevice so it can be a restart notification source. that's the whole vibe. 🦋

---

✨ SYNOPSIS ✨

void qcom_add_ssr_subdev (struct rproc *rproc , struct qcom_rproc_ssr
*ssr , const char *ssr_name );

three args, void return, no notes. slay. ✨

---

🌸 ARGUMENTS 🌸

• rproc — the rproc handle. it's giving main character energy because everything flows through it 🫶
• ssr — the SSR subdevice handle. this is the little subdevice we're adding 💖
• ssr_name — the identifier used for notifications originating from rproc. label your children, bestie 🎀

---

💜 DESCRIPTION 💜

so here's the tea ☕ — once the ssr is registered with the rproc, SSR events get sent out to all registered listeners for the remoteproc whenever its SSR events happen. and which events are those? so glad you asked:

• pre startup
• post startup
• pre shutdown
• post shutdown

that's the whole cycle, no cap. everybody who signed up gets the notification, fr fr. 🔥

---

🦋 SEE ALSO 🦋

kernel file ./drivers/remoteproc/qcom_common.c, plus the whole friend group:

• struct minidump_region(9)
• struct minidump_subsystem(9)
• struct minidump_global_toc(9)
• qcom_add_glink_subdev(9)
• qcom_remove_glink_subdev(9)
• qcom_register_dump_segments(9)
• qcom_add_smd_subdev(9)
• qcom_remove_smd_subdev(9)
• qcom_register_ssr_notifier(9)
• qcom_unregister_ssr_notifier(9)
• qcom_remove_ssr_subdev(9)
• qcom_add_pdm_subdev(9)
• qcom_remove_pdm_subdev(9)

iykyk 👑

---

ngl this page lives in ./drivers/remoteproc, and it's dated October 2026 — so yeah, qcom_add_ssr_subdev(9), see you in the group chat 💅💖✨

okay bye bestie, go register that subdevice 🧚🌈🍓