qcom_remove_smd_subdev(9)

🎀 NAME 🎀

qcom_remove_smd_subdev — bestie, this is the one that removes the smd subdevice from rproc 💅

Like, the whole entire job of this function is: take that SMD subdevice and yeet it out of the rproc. That's it. That's the vibe. ✨

🌈 SYNOPSIS 🌈

void qcom_remove_smd_subdev (struct rproc *rproc , struct
qcom_rproc_subdev *smd );

Note the void — she gives nothing back, no return value, no receipts, just does the thing and dips 😌

🦋 ARGUMENTS 🦋

• rproc — the rproc handle 🫶 literally just the rproc, that's the whole description, no cap
• smd — the SMD subdevice to remove 👋 this is the one getting un-invited from the rproc party

💜 SEE ALSO 💜

Okay so if you're doing the whole subdev tour, here's the full squad, all in Kernel file ./drivers/remoteproc/qcom_common.c 📁:

• 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_register_ssr_notifier(9)
• qcom_unregister_ssr_notifier(9)
• qcom_add_ssr_subdev(9)
• qcom_remove_ssr_subdev(9)
• qcom_add_pdm_subdev(9)
• qcom_remove_pdm_subdev(9)

iykyk — if you're calling the remove, you probably already called the add. qcom_add_smd_subdev(9) is literally right there in the list. balance restored 🙈

⭐ sign-off ⭐

This lil masterpiece lives in the Kernel API Manual, section 9, and it's dated October 2026 ⏰ — pulled straight outta ./drivers/remoteproc. slay, go remove some subdevices responsibly bestie 💖🔥