STRUCT HI3660_MBOX(9)

💖 NAME 💖

struct hi3660_mbox — the Hi3660 mailbox controller data, aka the little struct that holds the whole controller together 🎀

This is your friendly neighborhood page from the Kernel API Manual, bestie — yes, the kernel has its own manual and yes it's iconic ✨

---

🦋 SYNOPSIS 🦋

struct hi3660_mbox {
    struct device *dev;
    void __iomem *base;
    struct mbox_chan chan[MBOX_CHAN_MAX];
    struct hi3660_chan_info mchan[MBOX_CHAN_MAX];
    struct mbox_controller controller;
 };

Like, that's the whole vibe right there — five fields, no cap, copy it exactly 💅

---

🌸 Members 🌸

• dev — the device this whole thing is attached to. It's giving "who do I belong to" energy 🫶
• base — the base address of the register mapping region. The coordinates of the mailbox's whole situation, fr fr ⭐
• chan — representation of the channels in the mailbox controller. An array of struct mbox_chan, sized MBOX_CHAN_MAX — one seat per channel, periodt 🎀
• mchan — representation of the channel info. An array of struct hi3660_chan_info, also sized MBOX_CHAN_MAX. The lore behind each channel 🔥
• controller — representation of a communication channel controller. This is the main character — the struct mbox_controller holding it all down 👑

---

✨ DESCRIPTION ✨

Okay so boom: the mailbox controller includes 32 channels and can allocate a channel for message transferring 💌

That's literally it, that's the whole job — 32 channels, allocate one, move your messages, slay 💅

---

👀 SEE ALSO 👀

• Kernel file ./drivers/mailbox/hi3660-mailbox.c — go read the source, iykyk 🧚
• struct hi3660_chan_info(9) — the per-channel info struct, the sequel you need to read next 💜

---

ngl bestie, if you're touching this struct you should probably go read hi3660_chan_info too — they're literally a package deal 🙈

---

That's the page! Source lives in ./drivers/mailbox, dated October 2026 — tysm for reading, ily, go forth and transfer messages 🦋✨💖