STRUCT MHUV2_PROTOCOL_OPS(9)

✨ struct mhuv2_protocol_ops — MHUv2 operations ✨

okay bestie, this is the Kernel API Manual entry for struct mhuv2_protocol_ops, and it's honestly such a vibe — it's the little ops table that every MHUv2 transport protocol has to fill in. no cap. 🎀

---

🌸 NAME 🌸

struct mhuv2_protocol_ops — MHUv2 operations 💅

---

🦋 SYNOPSIS 🦋

okay so here's the whole struct, literally copy-paste this energy:

struct mhuv2_protocol_ops {
    int (*rx_startup)(struct mhuv2 *mhu, struct mbox_chan *chan);
    void (*rx_shutdown)(struct mhuv2 *mhu, struct mbox_chan *chan);
    void *(*read_data)(struct mhuv2 *mhu, struct mbox_chan *chan);
    void (*tx_startup)(struct mhuv2 *mhu, struct mbox_chan *chan);
    void (*tx_shutdown)(struct mhuv2 *mhu, struct mbox_chan *chan);
    int (*last_tx_done)(struct mhuv2 *mhu, struct mbox_chan *chan);
    int (*send_data)(struct mhuv2 *mhu, struct mbox_chan *chan, void
*arg);
 };

👑 Members 👑

• rx_startup — the startup callback for the receiver. she's getting ready, main character energy ✨
• rx_shutdown — the shutdown callback for the receiver. bye bestie 🫶
• read_data — reads and clears newly available data. grab it and wipe it, lowkey tidy 💖
• tx_startup — startup callback for receiver. (and yes, the page literally says receiver here, I'm just the messenger 🙈)
• tx_shutdown — shutdown callback for receiver. (again, receiver — that's what it says, not me 💀)
• last_tx_done — reports back whether the last tx is completed or not. the vibe check for your transmission 🌈
• send_data — sends data to the receiver. slay, deliver the goods 📬

---

🔥 Description 🔥

every single transport protocol must provide an implementation of the operations listed up here. no skipping, no shortcuts, no "I'll do it later" — like, it's giving mandatory, periodt. 💅

---

🌟 SEE ALSO 🌟

• Kernel file ./drivers/mailbox/arm_mhuv2.c
• struct mhuv2(9)

---

and that's the whole page, bestie — sourced from ./drivers/mailbox, dated October 2026. go forth and implement your ops, ily 🧚💜