cc_do_send_request(9)

💖 cc_do_send_request(9) 💖

okay so welcome to the cc_do_send_request(9) page from the Kernel API Manual — this is the lowkey iconic little function that enqueues a caller request to crypto hardware, and it has a very specific vibe check: it needs to be called with the HW lock held and PM running 🫶

🌸 NAME 🌸

cc_do_send_request — enqueue caller request to crypto hardware. Need to be called with the HW lock held and PM running, fr fr 💅

⚠️ bestie, this is the fine print: call it with the HW lock held and PM running. That part is not optional 😭

✨ SYNOPSIS ✨

the signature is giving “void, no return drama”:

void cc_do_send_request (struct cc_drvdata *drvdata , struct
cc_crypto_req *cc_req , struct cc_hw_desc *desc , unsigned int len ,
bool add_comp );

🎀 ARGUMENTS 🎀

• drvdata — associated device driver context.
• cc_req — the request to enqueue.
• desc — the crypto sequence.
• len — the crypto sequence length.
• add_comp — If "true": add an artificial dout DMA to mark completion.

🦋 SEE ALSO 🦋

• Kernel file ./drivers/crypto/ccree/cc_request_mgr.c
• request_mgr_complete(9)
• send_request_init(9)

mwah 💋 this page is brought to you by source/version ./drivers/crypto/ccree, dated October 2026, and it’s the cc_do_send_request(9) manual — bye bestie, go enqueue responsibly 🎀✨