STRUCT K3_RING_FIFO_REGS(9)

🎀 struct k3_ring_fifo_regs 🎀

okay bestie, so this whole page is from the Kernel API Manual, and it's literally just about one struct: struct k3_ring_fifo_regs, aka The Ring Accelerator Queues Registers region. 💖 That's the name, that's the whole vibe — it's the register map for the queue-y part of the Ring Accelerator. No cap.

✨ SYNOPSIS ✨

here's the shape of it, exactly as it lives, no edits no notes:

struct k3_ring_fifo_regs {
    u32 head_data[128];
    u32 tail_data[128];
    u32 peek_head_data[128];
    u32 peek_tail_data[128];
};

like… four arrays of 128 u32s each. it's giving "wall of registers" energy and honestly? we respect it. 👑

🌸 Members 🌸

these are the four fields and what each one is, no gatekeeping:

• head_data — Ring Head Entry Data Registers 🌈
• tail_data — Ring Tail Entry Data Registers 💜
• peek_head_data — Ring Peek Head Entry Data Regs 🦋 (yes, the field name says peek and the description says Peek — iconic, consistent, leave it alone 🔥)
• peek_tail_data — Ring Peek Tail Entry Data Regs ⭐

heads and tails, regular and peeked. four flavours. that's the entire struct. slay. 💅

🫶 SEE ALSO 🫶

go read these next, they're all in the same friend group:

• the kernel file ./drivers/soc/ti/k3-ringacc.c — that's where the lore lives, iykyk 😭
• struct k3_ring_rt_regs(9)
• struct k3_ringacc_proxy_gcfg_regs(9)
• struct k3_ringacc_proxy_target_regs(9)
• struct k3_ring_state(9)
• struct k3_ring(9)
• struct k3_ringacc(9)
• struct k3_ringacc_soc_data(9)

so yeah 🎀 this page comes from ./drivers/soc/ti, dated October 2026, and it's yours truly, struct k3_ring_fifo_regs(9) from the Kernel API Manual. mwah, go read your registers bestie 💖✨🌸