STRUCT TI_MSGMGR_DESC(9)

💖 struct ti_msgmgr_desc(9) 💖

okay so this is a page from the Kernel API Manual, section 9 — yes bestie, we're in the kernel docs now, grab a snack 🍓

✨ NAME ✨

struct ti_msgmgr_desc — literally just the description of the message manager integration. that's the whole vibe. 🦋

🌸 SYNOPSIS 🌸

struct ti_msgmgr_desc {
    u8 queue_count;
    u8 max_message_size;
    u8 max_messages;
    u8 data_first_reg;
    u8 data_last_reg;
    u32 status_cnt_mask;
    u32 status_err_mask;
    bool tx_polled;
    int tx_poll_timeout_ms;
    const struct ti_msgmgr_valid_queue_desc *valid_queues;
    const char *data_region_name;
    const char *status_region_name;
    const char *ctrl_region_name;
    int num_valid_queues;
    bool is_sproxy;
};

like, that's the struct. that's her. main character energy fr 💅

🎀 Members 🎀

the fields, one by one, no skips 👑

• queue_count — Number of Queues. that's it, that's the count 🧚
• max_message_size — Message size in bytes. bytes!! not vibes, bytes.
• max_messages — Number of messages. how many messages we're dealing with 💌
• data_first_reg — First data register for proxy data region. the first one, bestie.
• data_last_reg — Last data register for proxy data region. and obviously this is the last one 🫶
• status_cnt_mask — Mask for getting the status value. mask on, status out ✨
• status_err_mask — Mask for getting the error value, if applicable. note the "if applicable" — sometimes she's just not relevant, and that's fine 😭
• tx_polled — Do I need to use polled mechanism for tx. the struct is literally asking itself. relatable.
• tx_poll_timeout_ms — Timeout in ms if polled. ms = milliseconds, keep up 💀
• valid_queues — List of Valid queues that the processor can access. valid ones only, we don't do invalid queues here 👑
• data_region_name — Name of the proxy data region.
• status_region_name — Name of the proxy status region.
• ctrl_region_name — Name of the proxy control region. that's all three regions accounted for, slay 🌈
• num_valid_queues — Number of valid queues. yes it's a different field from queue_count, don't come for me, that's just how it is 🙈
• is_sproxy — Is this an Secure Proxy instance? (the double-article is canon, we're keeping it, love that for the original author 💖)

---

🦋 Description 🦋

so this structure is used in of match data to describe how integration for a specific compatible SoC is done. that's the entire job. it's giving "I'm the blueprint for how this SoC wires up its message manager" and honestly? iconic ✨

⭐ SEE ALSO ⭐

kernel file ./drivers/mailbox/ti-msgmgr.c, plus the whole friend group:

• struct ti_msgmgr_valid_queue_desc(9)
• struct ti_queue_inst(9)
• struct ti_msgmgr_inst(9)
• ti_msgmgr_queue_get_num_messages(9)
• ti_msgmgr_queue_is_error(9)
• ti_msgmgr_queue_rx_interrupt(9)
• ti_msgmgr_queue_peek_data(9)
• ti_msgmgr_last_tx_done(9)
• ti_msgmgr_send_data(9)
• ti_msgmgr_queue_rx_irq_req(9)
• ti_msgmgr_queue_startup(9)
• ti_msgmgr_queue_shutdown(9)
• ti_msgmgr_of_xlate(9)
• ti_msgmgr_queue_setup(9)

go read them too, iykyk 💜

---

okay that's the page 💫 it lives in ./drivers/mailbox and it's dated October 2026 — so yeah, she's from the future, we stan a forward-thinking manpage 🌸🫶 go forth and describe your message manager integration, bestie 💅