STRUCT SEC_QUEUE_RING_CMD(9)

💖 struct sec_queue_ring_cmd(9) 💖

okay bestie, so this one's from the Kernel API Manual and it's literally the little info-pack that holds all the deets about a SEC hardware cmd ring ✨ like, it's giving "backstage pass for the ring" energy, and honestly? obsessed.

---

🌸 NAME 🌸

struct sec_queue_ring_cmd — store information about a SEC HW cmd ring 🎀

---

🦋 SYNOPSIS 🦋

struct sec_queue_ring_cmd {
    atomic_t used;
    struct mutex lock;
    struct sec_bd_info *vaddr;
    dma_addr_t paddr;
    void (*callback)(struct sec_bd_info *resp, void *ctx);
 };

no cap, that's the whole vibe right there ⭐

---

👑 Members 👑

• used — a local counter, and its whole job is the cheap little "is the ring empty tho?" check 🫶 like it's not doing the most, it's just doing a quick vibe check so nobody has to do the expensive thing.
• lock — this one's the bodyguard 💅 it protects against the read and write pointers getting adjusted at the same time, i.e. no two things messing with them simultaneously. iconic behaviour, honestly.
• vaddr — the virtual address for the ram pages used for the ring ✨ that's it, that's the whole thing.
• paddr — the physical address of the dma mapped region of ram used for the ring 🌈 yes bestie, physical, not virtual, don't mix them up, i'm begging 😭
• callback — the callback function that gets called when a ring element completes 🎉 like a little "you did it!!" moment for every element. main character energy fr fr.

---

💜 SEE ALSO 💜

• Kernel file ./drivers/crypto/hisilicon/sec/sec_drv.h
• struct sec_alg_tfm_ctx(9)
• struct sec_request(9)
• struct sec_request_el(9)
• struct sec_queue(9)
• struct sec_hw_sge(9)
• struct sec_hw_sgl(9)
• struct sec_dev_info(9)

---

ngl bestie, go read those before you start poking at the ring, iykyk 🙈

---

so yeah, that's the whole page!! mwah 💋 this little cutie lives over at ./drivers/crypto/hisilicon/sec and the date on it is October 2026 — catch you in the group chat, love you, bye 🧚‍♀️🍓💖