caam_drv_ctx_busy(9)

💅 caam_drv_ctx_busy(9) 💅

okay so this is a page from the Kernel API Manual, bestie — yes, the actual kernel, like the big one. sit down, hydrate, and let's get into it 🫶

---

✨ NAME ✨

caam_drv_ctx_busy — checks whether there's, like, way too much going on: either too many jobs are pending with CAAM, or too many CAAM responses are just sitting there waiting to be processed. it's the vibe check for congestion, basically 💀

---

🎀 SYNOPSIS 🎀

bool caam_drv_ctx_busy (struct caam_drv_ctx *drv_ctx );

✨ returns a bool, takes a struct caam_drv_ctx * named drv_ctx, that's the whole thing, no cap ✨

---

🦋 ARGUMENTS 🦋

• drv_ctx — the driver context for which the job is to be submitted. like, which context are we checking? this one. 👑

---

🌸 DESCRIPTION 🌸

Returns the CAAM congestion status as true/false — that's it, that's the function. lowkey iconic for how simple it is 🧚

so: true = congested (too many jobs pending with CAAM, or too many CAAM responses pending to be processed), false = we're chilling. main character energy either way 💖

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/crypto/caam/qi.h 👀
• caam_drv_ctx_init(9)
• caam_qi_enqueue(9)
• caam_drv_ctx_update(9)
• caam_drv_ctx_rel(9)
• qi_cache_alloc(9)
• qi_cache_free(9)

the whole friend group, fr fr — go read them too, iykyk 🎀

---

and that's the page!! brought to you by the fine folks over at ./drivers/crypto/caam, dated October 2026 🌈 mwah, go check your congestion status bestie 💅✨🦋