STRUCT CAAM_CTX(9)

💖 struct caam_ctx(9) 💖

okay bestie, welcome to the Kernel API Manual — this one's a struct page, she's a little technical but we're gonna slay it together 🫶

✨ NAME ✨

struct caam_ctx — the per-session context, aka the little vibe-holder that keeps track of one crypto session's whole situation 💅

🌸 SYNOPSIS 🌸

struct caam_ctx {
    struct caam_flc flc[NUM_OP];
    u8 key[CAAM_MAX_KEY_SIZE];
    dma_addr_t flc_dma[NUM_OP];
    dma_addr_t key_dma;
    enum dma_data_direction dir;
    struct device *dev;
    struct alginfo adata;
    struct alginfo cdata;
    unsigned int authsize;
    bool xts_key_fallback;
    struct crypto_skcipher *fallback;
 };

like, look at her. every field is doing something. main character struct energy fr fr 👑

🎀 Members 🎀

• flc — the Flow Contexts array. plural, she contains multitudes ✨
• key — the [authentication key], encryption key. yes both, she's versatile 💅
• flc_dma — I/O virtual addresses of the Flow Contexts 🦋
• key_dma — the I/O virtual address of the key 🔑
• dir — DMA direction used for mapping the key and the Flow Contexts 🧭
• dev — the dpseci device 🖥️
• adata — authentication algorithm details 🌸
• cdata — encryption algorithm details 🔐
• authsize — authentication tag size, a.k.a. the ICV / MAC size 🎀
• xts_key_fallback — true if a fallback tfm needs to be used because the xts key lengths aren't supported 😭 (yes, it's a whole thing)
• fallback — the xts fallback tfm 🫶

ngl bestie, if you're poking at xts_key_fallback you already know what you're doing — that flag only flips when the xts key lengths just aren't supported and the fallback tfm has to step in 💀

🦋 SEE ALSO 🦋

• Kernel file ./drivers/crypto/caam/caamalg_qi2.c
• struct caam_hash_ctx(9) — her cousin, go say hi 💖

and that's the whole page, bestie!! 🌈⭐💜 this iconic little number lives over at ./drivers/crypto/caam, dated October 2026, and yes the manual name is struct caam_ctx(9) — same as the title, she's consistent like that 💅✨🎀 go forth and map those DMA addresses 🦋🌸