STRUCT RING_BUF_MANAGER(9)

💖 struct ring_buf_manager(9) 💖

okay so this is from the Kernel API Manual, section 9 (kernel API, bestie, iykyk) — and it's literally just a helper structure that manages a ring buffer 🎀

---

✨ NAME ✨

struct ring_buf_manager — the helper structure whose whole job is managing a ring buffer 🌀 no cap

---

🌸 SYNOPSIS 🌸

struct ring_buf_manager {
    struct mutex mutex;
    void *ring_start;
    u32 ring_size;
    phys_addr_t ring_pa;
    u32 wptr;
 };

like… look at her. five fields. main character energy 💅

---

🦋 Members 🦋

• ring_start — the starting address of the ring buffer. that's where it all begins, fr fr ✨
• ring_size — how big the ring buffer is, measured in bytes (yes, bytes, not vibes) 📏
• ring_pa — the physical address of the ring buffer. physical, not virtual — important distinction, don't @ me 💀
• wptr — the index pointing to the last written entry in the ring buffer ✍️ so you always know where the writing left off

ngl the struct also has a mutex in there (struct mutex mutex;), it just doesn't get its own little member blurb in this list. i'm not gonna make one up for it because that would be lying and lying is not slay 🙈

---

🫶 SEE ALSO 🫶

• the kernel file ./drivers/crypto/ccp/tee-dev.h 👑
• struct tee_init_ring_cmd(9)
• enum tee_cmd_state(9)
• enum cmd_resp_state(9)
• struct tee_ring_cmd(9)

like a little friend group of crypto/ccp structures and enums 🧚 go read them too, they ate 💜

---

and that's the whole page, bestie — sourced from ./drivers/crypto/ccp, dated October 2026, still titled struct ring_buf_manager(9) because we respect the classics 🌈 mwah 💋