cc_send_request(9)

🦋 cc_send_request(9) — Kernel API Manual, bestie edition 🦋

Okay so this is the cc_send_request(9) page from the Kernel API Manual, and it's literally about one job: Enqueue caller request to crypto hardware. That's the whole main character energy of this function. No cap.

💖 NAME 💖

cc_send_request — Enqueue caller request to crypto hardware.

✨ SYNOPSIS ✨

int cc_send_request (struct cc_drvdata *drvdata , struct cc_crypto_req *cc_req , struct cc_hw_desc *desc , unsigned int len , struct crypto_async_request *req );

Bestie, that's the whole signature. Every type and pointer is doing its little slay. 💅

🎀 ARGUMENTS 🎀

• drvdata — Associated device driver context. It's the device driver's little context bubble.
• cc_req — The request to enqueue. This is the thing going into the queue.
• desc — The crypto sequence.
• len — The crypto sequence length.
• req — Asynchronous crypto request.

🌸 RETURN 🌸

Returns -EINPROGRESS or error. That's it — that's the return tea. 💅

💅 SEE ALSO 💅

Kernel file ./drivers/crypto/ccree/cc_request_mgr.h — that's the one and only see-also on this page, iykyk.

Big cute sign-off from ./drivers/crypto/ccree, October 2026 edition — cc_send_request(9) is out, stay hydrated and enqueue responsibly 🫶✨