mbox_client_txdone(9)

💌 mbox_client_txdone(9) — a Kernel API Manual moment

okay so bestie, welcome to the mbox_client_txdone(9) page, straight out of the Kernel API Manual. this is the one where the client gets to drive the TX state machine, and honestly? main character energy. let's get into it 🎀

---

✨ NAME ✨

mbox_client_txdone — the way for a client to run the TX state machine.

like, literally the whole point. no cap. 💅

---

🦋 SYNOPSIS 🦋

void mbox_client_txdone (struct mbox_chan *chan , int r );

that's it. that's the whole signature. two args, returns nothing, slays quietly. ✨

---

🌸 ARGUMENTS 🌸

• chan — the mailbox channel that's been assigned to this client. it's yours, bestie, own it. 👑
• r — the success status of the last transmission. so like, did it work or not. 💀

---

💖 DESCRIPTION 💖

okay so here's the vibe: the client/protocol has received some 'ACK' packet, and now it's telling the API that the last packet was sent successfully. that's the whole move. 🫶

⚠️ but listen — this only works if the controller can't sense TX-Done. like, if your controller already knows, this isn't the function for you. read the room, iykyk. 🙈

---

🔥 SEE ALSO 🔥

kernel file ./drivers/mailbox/mailbox.c — go read it, it's giving lore:

• mbox_chan_received_data(9)
• mbox_chan_txdone(9)
• mbox_client_peek_data(9)
• mbox_chan_tx_slots_available(9)
• mbox_send_message(9)
• mbox_flush(9)
• mbox_bind_client(9)
• mbox_request_channel(9)
• mbox_free_channel(9)
• mbox_controller_register(9)
• mbox_controller_unregister(9)
• devm_mbox_controller_register(9)

the whole friend group fr fr. go say hi. 🌈

---

and that's the page!! mwah 💋 this absolute icon lives over in ./drivers/mailbox, dated October 2026, and it's titled mbox_client_txdone(9) — go forth and run that TX state machine, bestie, you're gonna ate. ⭐💜