STRUCT MBOX_INFO(9)

💌 struct mbox_info(9) — the kernel API page for struct mbox_info

okay so bestie, buckle up, because this is the little struct that makes the mailbox channels between your cores actually talk to each other. it's called struct mbox_info, and it is, fr fr, just "mailbox channel data" — that's the whole vibe. 🎀

---

✨ NAME ✨

struct mbox_info — mailbox channel data 💅

---

🦋 SYNOPSIS 🦋

struct mbox_info {
    unsigned char rx_mc_buf[MBOX_CLIENT_BUF_MAX];
    unsigned char tx_mc_buf[MBOX_CLIENT_BUF_MAX];
    struct zynqmp_r5_core *r5_core;
    struct work_struct mbox_work;
    struct mbox_client mbox_cl;
    struct mbox_chan *tx_chan;
    struct mbox_chan *rx_chan;
 };

no cap, that's the whole shape of it. copy it exactly, don't get creative with it 😭

---

🌸 Members 🌸

• rx_mc_buf — the buffer where we copy data coming in from the mailbox rx channel. it's unsigned char rx_mc_buf[MBOX_CLIENT_BUF_MAX], so it's got room for MBOX_CLIENT_BUF_MAX bytes of incoming goodness 💖
• tx_mc_buf — the buffer where we copy data going out to the mailbox tx channel. also unsigned char tx_mc_buf[MBOX_CLIENT_BUF_MAX]. matching energy, iconic 🫶
• r5_core — a pointer (struct zynqmp_r5_core *) to the r5_core that this mailbox belongs to. it's like, "whose mailbox is this anyway?" — this member answers that ✨
• mbox_work — a struct work_struct that lets us schedule work after data shows up from the mailbox. so when the data lands, this is what queues up the follow-through 💅
• mbox_cl — the mailbox client, a struct mbox_client. yes bestie, that's the client side of the relationship 🤝
• tx_chan — a struct mbox_chan * — the mailbox tx channel. outgoing mail goes here 📤
• rx_chan — a struct mbox_chan * — the mailbox rx channel. incoming mail lands here 📥

ngl, rx_chan and tx_chan being separate is the whole point — one for the mail you send, one for the mail you get. main character and supporting character, both essential 👑

---

🔥 SEE ALSO 🔥

okay so if you wanna go deeper (and you should, we're obsessed with context), the kernel file is ./drivers/remoteproc/xlnx_r5_remoteproc.c, and here's the full bestie roll call — all of these are (9) man pages:

• struct mem_bank_data(9)
• struct zynqmp_sram_bank(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)
• zynqmp_r5_get_tcm_node(9)

---

and that's the whole page, bestie — 10/10, no notes, ate and left no crumbs 💜

this came out of ./drivers/remoteproc and it's dated October 2026 ✨ go read the other pages, ily, bye 🧚