spu_rx_callback(9)

✨ NAME ✨

okay so bestie, this is spu_rx_callback(9) from the Kernel API Manual — it's the callback from the mailbox framework with a SPU response. That's the whole main-character job: mailbox framework sends the SPU response, and this callback is the one receiving it. 💅

🌸 SYNOPSIS 🌸

void spu_rx_callback (struct mbox_client *cl , void *msg );

that's the signature, no cap ✨

🎀 ARGUMENTS 🎀

• cl — the mailbox client structure for the SPU driver, aka the client-side setup bestie 🫶
• msg — the mailbox message containing the SPU response, aka the actual tea being delivered 💌

🦋 SEE ALSO 🦋

go check out these icons, fr fr:

• Kernel file ./drivers/crypto/bcm/cipher.c
• 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)
• handle_ahash_resp(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)
• 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)

source/version vibes: this page lives under ./drivers/crypto/bcm, dated October 2026, and it's spu_rx_callback(9) signing off — mwah, bye bestie 💖✨