STRUCT STI_MBOX_DEVICE(9)

💌 struct sti_mbox_device(9) — the STi Mailbox device data glow-up

okay so bestie, we're in the Kernel API Manual today and this is the page for struct sti_mbox_device — it's literally the STi Mailbox device data and it's kind of iconic ngl 🎀

---

✨ NAME ✨

struct sti_mbox_device — STi Mailbox device data. that's it, that's the vibe 💅

---

🦋 SYNOPSIS 🦋

struct sti_mbox_device {
    struct device           *dev;
    struct mbox_controller  *mbox;
    void __iomem            *base;
    const char              *name;
    u32 enabled[STI_MBOX_INST_MAX];
    spinlock_t lock;
 };

like, that's the whole thing. she's compact, she's structured, she ate 🔥

---

🌸 Members 🌸

okay let's go through the members one by one, no skipping, we don't do that here 🫶

• dev — the Device to which it is attached. her home base fr fr.
• mbox — Representation of a communication channel controller. the whole controller vibe 👑
• base — Base address of the register mapping region. where the registers actually live, lowkey important.
• name — Name of the mailbox. she has a name, obviously 💖
• enabled — Local copy of enabled channels. a little local record of who's enabled ✨
• lock — Mutex protecting enabled status. guards the enabled status, do not skip the locking bestie 😭

---

💜 Description 💜

so, the lore: an IP Mailbox is currently composed of 4 instances. Each instance is currently composed of 32 channels. This means that we have 128 channels per Mailbox — yes, the math is mathing, 4 × 32 = 128, periodt 💅

and a channel can be used for TX or RX. pick your fighter 🦋

---

🌈 SEE ALSO 🌈

go read these next, iykyk:

• Kernel file ./drivers/mailbox/mailbox-sti.c
• struct sti_mbox_pdata(9)
• struct sti_channel(9)

---

not me getting emotional over a mailbox driver 🥹 go forth and read the source, bestie, you've got this 💪

---

and that's the page!! sign-off time: this lives under ./drivers/mailbox and the date on it is October 2026 ⭐ catch you in the kernel, mwah 💋🎀