qcom_add_sysmon_subdev(9)

okay so bestie, welcome to the qcom_add_sysmon_subdev(9) page from the Kernel API Manual ✨ This is the kernel-API moment where you create a sysmon subdev for the given remoteproc. No cap, it’s giving “make the sysmon situation official” energy 💅

💖 NAME 💖

qcom_add_sysmon_subdev — create a sysmon subdev for the given remoteproc. That’s the whole vibe: a sysmon subdev gets created for the remoteproc you hand over 🫶

✨ SYNOPSIS ✨

Here’s the signature, exactly as it shows up — no edits, no “fixing” it, periodt:

struct qcom_sysmon * qcom_add_sysmon_subdev (struct rproc *rproc , const char *name , int ssctl_instance );

🎀 ARGUMENTS 🎀

• rproc — the rproc context you’re associating the subdev with. That’s the main-character context, iykyk.
• name — the name of this subdev, and it’s the name to use in SSR. Cute, labeled, ready.
• ssctl_instance — the instance id of the ssctl QMI service. Not me lowkey memorizing instance ids 🙈

🌸 RETURN 🌸

You get a fresh qcom_sysmon object back. If it fails? You get an error pointer on failure. That’s the whole return vibe, fr fr 💀

🦋 SEE ALSO 🦋

The kernel file is ./drivers/remoteproc/qcom_sysmon.c, and it’s bringing the whole friend group:

• 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_start(9)
• sysmon_notify(9)
• qcom_remove_sysmon_subdev(9)
• qcom_sysmon_shutdown_acked(9)
• sysmon_probe(9)
• sysmon_remove(9)

Cute lil footer moment: source/version is ./drivers/remoteproc, date is October 2026, and the footer title is qcom_add_sysmon_subdev(9). Catch u later, bestie — stay iconic 🫶✨