zynqmp_r5_get_tcm_node(9)

💅 zynqmp_r5_get_tcm_node — ok bestie let me put you on

so this is a page from the Kernel API Manual, section 9 — yes we're in the deep kernel lore today, and honestly? iconic of you for showing up 🫶

---

✨ NAME ✨

zynqmp_r5_get_tcm_node — get that TCM info, bestie 🎀

ok so the ideal timeline is literally this: this function parses the tcm node and stores that info in the r5_core instance. that's the dream. that's the vision. 🔥

but right now? for now, Hardcoded TCM information is used 🙈 — not a vibe, but it is what it is. this approach is used because the TCM bindings for system-dt are legit still being developed. so yeah, we're on the hardcoded arc until the binding glow-up drops 💀

---

🌸 SYNOPSIS 🌸

int zynqmp_r5_get_tcm_node (struct zynqmp_r5_cluster *cluster );

like — one argument, spits out an int. simple. clean. main character energy 👑

---

🦋 ARGUMENTS 🦋

• cluster — pointer to a zynqmp_r5_cluster type object. that's it, that's the whole input 🎀

---

⭐ RETURN ⭐

• 0 — success, we ate, no cap 💖
• < 0 — an error code, failure, not the slay we wanted 😭

---

🌈 SEE ALSO 🌈

go read the kernel file itself, it's literally right here:

./drivers/remoteproc/xlnx_r5_remoteproc.c

and while you're there, here's the whole friend group 🫶:

• struct mem_bank_data(9)
• struct zynqmp_sram_bank(9)
• struct mbox_info(9)
• struct rsc_tbl_data(9)
• struct xlnx_rproc_crash_report(9)
• struct zynqmp_r5_core(9)
• struct zynqmp_r5_cluster(9)
• event_notified_idr_cb(9)
• handle_event_notified(9)
• zynqmp_r5_mb_rx_cb(9)
• zynqmp_r5_setup_mbox(9)
• zynqmp_r5_rproc_prepare(9)
• zynqmp_r5_rproc_unprepare(9)
• zynqmp_r5_alloc_rproc_core(9)

---

⚠️ friendly reminder bestie: the TCM info you're getting back is hardcoded right now, not parsed from the tcm node. the real parsing is coming once those system-dt TCM bindings land. don't @ me, @ the bindings 💅

---

ok that's the page!! source is ./drivers/remoteproc, dated October 2026 — mwah, go touch some registers, ily, bye 🧚💜