sysmon_start(9)

💖 sysmon_start(9) 💖

okay bestie, this page is from the Kernel API Manual — yes, that one. It’s giving kernel callback realness, and we’re gonna walk through it together 🫶

---

🌸 NAME 🌸

sysmon_start — start callback for the sysmon remoteproc subdevice ✨

---

✨ SYNOPSIS ✨

int sysmon_start (struct rproc_subdev *subdev );

---

🎀 ARGUMENTS 🎀

• subdev — instance of the sysmon subdevice. That’s the subdevice bestie we’re starting up 💅

---

🦋 DESCRIPTION 🦋

So basically, sysmon_start informs all the listners of sysmon notifications that the rproc associated to subdev has booted up. (Yes, the original says listners — keeping that detail exactly, no cap 😭💀)

The rproc that booted up also needs to know which rprocs are already up and running, so it sends start notifications on behalf of all the online rprocs. Everyone gets the memo, fr fr 🌈

---

🔥 SEE ALSO 🔥

Kernel file ./drivers/remoteproc/qcom_sysmon.c

• sysmon_send_event(9)
• sysmon_request_shutdown(9)
• ssctl_request_shutdown(9)
• ssctl_send_event(9)
• ssctl_new_server(9)
• ssctl_del_server(9)
• sysmon_notify(9)
• qcom_add_sysmon_subdev(9)
• qcom_remove_sysmon_subdev(9)
• qcom_sysmon_shutdown_acked(9)
• sysmon_probe(9)
• sysmon_remove(9)

---

Source/version is ./drivers/remoteproc, and the date is October 2026 — okay bye bestie, sysmon_start(9) out 💜🎀✨