qcom_register_dump_segments(9)

qcom_register_dump_segments(9) 💅✨

okay so bestie, welcome to this lil Kernel API Manual moment — it’s giving “remoteproc coredump registration” and I’m obsessed. no cap, this page is about qcom_register_dump_segments, and it’s short but iconic. 🫶

---

🌸 NAME 🌸

qcom_register_dump_segments — register segments for coredump. literally that’s the whole name vibe. 💖

✨ SYNOPSIS ✨

int qcom_register_dump_segments (struct rproc *rproc , const struct
       firmware *fw );

🎀 ARGUMENTS 🎀

• rproc — the remoteproc handle u pass in, bestie. 💅
• fw — the firmware header. that’s the one. 🦋

💫 DESCRIPTION 💫

okay so what it does: it registers all the segments of the ELF into the remoteproc coredump segment list. that’s it, that’s the whole slay. ⭐

🔥 RETURN 🔥

• 0 on success — yayyy, we love a clean win 💖
• negative errno on failure — it’s giving “not today” 😭

🌈 SEE ALSO 🌈

Kernel file: ./drivers/remoteproc/qcom_common.c

go give these a look too, bestie:

• struct minidump_region(9)
• struct minidump_subsystem(9)
• struct minidump_global_toc(9)
• qcom_add_glink_subdev(9)
• qcom_remove_glink_subdev(9)
• qcom_add_smd_subdev(9)
• qcom_remove_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)

---

mwah 💋 this lil page’s footer energy: source/version is ./drivers/remoteproc, date is October 2026, and the manual tag is qcom_register_dump_segments(9). bye bestie, go register those segments 🫶✨