handle_ahash_resp(9)

handle_ahash_resp(9) 💅

okay so bestie, we're in the Kernel API Manual and this is the page for handle_ahash_resp. It's giving "tiny helper, big crypto energy," and the whole point is handling a SPU response for a hash request. Let's get into it. 🦋

✨ NAME ✨

handle_ahash_resp — Process a SPU response message for a hash request. It checks whether the entire crypto API request has been processed, and if so, it invokes post processing on the result. No cap, that's the whole job. 💖

🎀 SYNOPSIS 🎀

Signature, exactly as it appears:

void handle_ahash_resp (struct iproc_reqctx_s *rctx );

So it returns void, and it takes one pointer to a struct iproc_reqctx_s named rctx. periodt. 💅

🌸 ARGUMENTS 🌸

• rctx — the crypto request context. That's the one and only argument, bestie. She's carrying the context for this crypto request. 👑

🦋 SEE ALSO 🦋

Kernel file: ./drivers/crypto/bcm/cipher.c. The whole friend group is here — every reference, no skips:

• select_channel(9)
• spu_skcipher_rx_sg_create(9)
• spu_skcipher_tx_sg_create(9)
• handle_skcipher_req(9)
• handle_skcipher_resp(9)
• spu_ahash_rx_sg_create(9)
• spu_ahash_tx_sg_create(9)
• handle_ahash_req(9)
• spu_hmac_outer_hash(9)
• ahash_req_done(9)
• spu_aead_rx_sg_create(9)
• spu_aead_tx_sg_create(9)
• handle_aead_req(9)
• handle_aead_resp(9)
• spu_chunk_cleanup(9)
• finish_req(9)
• spu_rx_callback(9)
• skcipher_enqueue(9)
• spu_no_incr_hash(9)
• aead_gcm_esp_setkey(9)
• rfc4543_gcm_esp_setkey(9)
• aead_ccm_esp_setkey(9)
• spu_functions_register(9)
• spu_mb_init(9)

🫶 that's the whole vibe, bestie: source/version ./drivers/crypto/bcm, dated October 2026, and this page is handle_ahash_resp(9). mwah 💋